rearranged directory structure, automaterialize to automationCondition

docker-compose.yaml

@@ -29,23 +29,24 @@ services:
   # Multiple containers like this can be deployed separately - each just needs to run on
   # its own port, and have its own entry in the workspace.yaml file that's loaded by the
   # webserver.
-  dagster_user_code_gtfs:
+  dagster_code:
     build:
       context: .
-      dockerfile: ./Dockerfile_user_code_gtfs
-    container_name: dagster_user_code_gtfs
-    image: dagster_user_code_gtfs
+      dockerfile: ./Dockerfile_dagster_code
+    container_name: dagster_code
+    image: dagster_code
     restart: always
     environment:
       DAGSTER_POSTGRES_USER: ${POSTGRES_USER}
       DAGSTER_POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
       DAGSTER_POSTGRES_DB: ${POSTGRES_DB}
-      DAGSTER_CURRENT_IMAGE: 'dagster_user_code_gtfs'
+      DAGSTER_CURRENT_IMAGE: 'dagster_code'
       MOBILITY_DB_REFRESH_TOKEN: ${MOBILITY_DB_REFRESH_TOKEN}
     env_file:
       - .env
     volumes:
       - ./data:/opt/dagster/app/data
+      - ./config:/opt/dagster/app/config
     networks:
       - dagster
 
@@ -81,7 +82,7 @@ services:
     depends_on:
       dagster_postgresql:
         condition: service_healthy
-      dagster_user_code_gtfs:
+      dagster_code:
         condition: service_started
 
   # This service runs the dagster-daemon process, which is responsible for taking runs
@@ -109,7 +110,7 @@ services:
     depends_on:
       dagster_postgresql:
         condition: service_healthy
-      dagster_user_code_gtfs:
+      dagster_code:
         condition: service_started
 
 networks: