Description
When deploying Catalyst with Docker Compose, changing the backend service port through the PORT environment variable does not update the frontend nginx proxy configuration.
The backend container starts successfully and listens on the configured port, but the frontend nginx configuration still uses a hardcoded upstream port (3000), causing all API requests to fail with 502 Bad Gateway.
Environment
- Catalyst version: latest Docker image
- Deployment method: Docker Compose
- Frontend: nginx-based frontend container
- Backend: configured with custom
PORT environment variable
Actual behavior
The backend correctly starts on the configured port.
However, the frontend nginx configuration still contains a hardcoded upstream:
proxy_pass http://<backend-host>:3000;
Description
When deploying Catalyst with Docker Compose, changing the backend service port through the
PORTenvironment variable does not update the frontend nginx proxy configuration.The backend container starts successfully and listens on the configured port, but the frontend nginx configuration still uses a hardcoded upstream port (
3000), causing all API requests to fail with502 Bad Gateway.Environment
PORTenvironment variableActual behavior
The backend correctly starts on the configured port.
However, the frontend nginx configuration still contains a hardcoded upstream: