You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`LOG_DIR`: Directory for log files (default: `logs`)
229
+
-`ENABLE_FILE_LOGGING`: Boolean flag to control file logging in production
230
+
231
+
### ECS Deployment Notes
232
+
When deploying to ECS, ensure:
233
+
1.`NODE_ENV=production` is set
234
+
2.`ENABLE_FILE_LOGGING` is either unset or set to `false` for read-only filesystems
235
+
3. Container logging is configured to collect stdout/stderr logs
236
+
209
237
## Further Documentation
210
238
211
239
For more detailed technical information, please see the documents in the `docs/` directory:
@@ -228,3 +256,13 @@ For more detailed technical information, please see the documents in the `docs/`
228
256
```
229
257
230
258
-**API Authentication Errors**: Ensure Auth0 credentials (`AUTH0_URL`, `AUTH0_CLIENT_ID`, `AUTH0_CLIENT_SECRET`, `AUTH0_AUDIENCE`) in your `.env` file are valid and not expired.
259
+
260
+
-**ECS Deployment - Read-only Filesystem Error**: If the application fails to start in ECS with errors about creating a 'logs' directory:
261
+
- Ensure `NODE_ENV=production` is set in your ECS task definition
262
+
- Verify `ENABLE_FILE_LOGGING` is not set or is set to `false`
263
+
- Check that your ECS task definition is configured to collect logs from stdout/stderr
264
+
265
+
-**Logging Issues**:
266
+
-**No log files in development**: Check that `ENABLE_FILE_LOGGING` is not set to `false`
267
+
-**File permission errors**: Ensure the application has write permissions to the `LOG_DIR` directory
268
+
-**Missing logs in production**: Verify your container logging configuration is collecting stdout/stderr output
0 commit comments