Clean up docker-compose.yml#41
Merged
Merged
Conversation
…17 (match prod), remove unused anchors
JuanVqz
force-pushed
the
feature/docker-compose-cleanup
branch
from
July 23, 2026 22:44
074e008 to
98427a6
Compare
etagwerker
approved these changes
Jul 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Small housekeeping on
docker-compose.yml, split out of the Ruby patch bump (#40) to keep that PR focused.Changes
version: "3.9"key (Compose v2 ignores it and warns).dbimage frompostgres:10.9(EOL) topostgres:17, matching the production Postgres version (17.9).&web/&envs(defined but never referenced).Notes
postgresql-client-14(PG_MAJOR: 14). That's intentional: libpq is forward-compatible, so a v14 client connects to a v17 server fine. Bumping the client to 17 would require adding the PGDG apt repo, a larger change left out here.docker compose configvalidates clean.db_datavolume must rundocker compose down -v(drops local dev data) beforeupwill start. Fresh clones are unaffected.depends_onhealthcheck (wait for Postgres ready, not just container start) was considered but left out as a larger, separate change.