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.
[codex] Use managed Redis and Postgres in Coolify compose #279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
[codex] Use managed Redis and Postgres in Coolify compose #279
Changes from all commits
fe48ae7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
compose.local.yamlis loaded directly withcompose.yaml(for example by tools using the overlay rather thanscripts/docker-compose.sh), Compose merges theenvironmentmaps, so the basePOSTGRES_URLentry remains. With the.env.exampledefault copied to.env, the web and worker containers keeppostgresql://...@127.0.0.1:5432/...and fail to connect to the localpostgresservice even though this overlay starts and waits for it; the wrapper masks this by exporting a Docker-network URL, but the overlay itself should also overridePOSTGRES_URLlike it does for Redis.Useful? React with 👍 / 👎.