Fixes #4: Resolved 502 Bad Gateway error by updating docker-compose.yml #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This pull request fixes Issue #4, where the Nginx reverse proxy was returning a 502 Bad Gateway error due to FastAPI services not being ready before startup.
Changes Made:
pg_isready
health checks formovie_db
andcast_db
to ensure they are available before dependent services start.depends_on
Behavior: Now waits for database readiness instead of just container startup.restart: always
for all services to improve reliability.postgres_data_cast
volume declaration.How to Test: