Moving env file back so Dockerfile.frontend can access

Author: jeffmaki

docker-compose.deploy.yml

@@ -66,7 +66,7 @@ services:
     # Workspaces backend currently lives in the TM. Emulate a separate server for now:
     image: ${WS_DOCKER_REGISTRY}/workspaces-tasks-backend:${WS_DOCKER_TAG}
     restart: always
-    env_file: tasking-manager.env
+    env_file: tasking-manager/tasking-manager.env
     environment:
       GUNICORN_CMD_ARGS: "--workers 5 --threads 5 --timeout 179"
     labels:
@@ -169,7 +169,7 @@ services:
   tasks-backend:
     image: ${WS_DOCKER_REGISTRY}/workspaces-tasks-backend:${WS_DOCKER_TAG}
     restart: always
-    env_file: tasking-manager.env
+    env_file: tasking-manager/tasking-manager.env
     environment:
       GUNICORN_CMD_ARGS: "--workers 5 --threads 5 --timeout 179"
     labels: