Problem
The current Docker configuration uses multiple environment variables representing frontend origin and CORS-related configuration:
FRONTEND_URLFRONTEND_ORIGINCORS_ALLOWED_ORIGINS
These variables are passed to different services and appear to serve closely related purposes.
This creates multiple configuration sources that contributors must understand and maintain when changing frontend deployment URLs.
Impact
Potential issues include:
- Increased configuration complexity.
- Higher risk of inconsistent values between services.
- Additional maintenance burden when deployment URLs change.
- Confusion for new contributors during environment setup.
Suggested Investigation
Review:
- Which variables are actively consumed by each service.
- Whether any variables are redundant.
- Whether a common naming convention can be adopted.
- Whether documentation accurately describes the required configuration.
Proposed Changes
-
Audit usage of:
FRONTEND_URLFRONTEND_ORIGINCORS_ALLOWED_ORIGINS
-
Identify variables that represent the same frontend endpoint.
-
Standardize naming where practical.
-
Update service configuration to use a consistent convention.
-
Update:
.env.exampledocker-compose.yml- setup documentation
-
Document the purpose of each remaining variable to reduce contributor confusion.
Expected Outcome
Frontend origin configuration should be clearly documented and use a consistent naming strategy wherever possible.
Problem
The current Docker configuration uses multiple environment variables representing frontend origin and CORS-related configuration:
FRONTEND_URLFRONTEND_ORIGINCORS_ALLOWED_ORIGINSThese variables are passed to different services and appear to serve closely related purposes.
This creates multiple configuration sources that contributors must understand and maintain when changing frontend deployment URLs.
Impact
Potential issues include:
Suggested Investigation
Review:
Proposed Changes
Audit usage of:
FRONTEND_URLFRONTEND_ORIGINCORS_ALLOWED_ORIGINSIdentify variables that represent the same frontend endpoint.
Standardize naming where practical.
Update service configuration to use a consistent convention.
Update:
.env.exampledocker-compose.ymlDocument the purpose of each remaining variable to reduce contributor confusion.
Expected Outcome
Frontend origin configuration should be clearly documented and use a consistent naming strategy wherever possible.