Updated Postgres container to Postgres 14 #82
Merged
Conversation
This file contains 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
… separately Added a make target to remove the pg data volume; this will make it easier for people to upgrade PG
cnk
changed the title
laymonage
reviewed
Dec 24, 2024
Co-authored-by: sage <[email protected]>
zerolab
approved these changes
Dec 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today I found I had to upgrade my Postgres version from 12 to 1. This is because bakerydemo is now running Django 5.1 which dropped support for postgres 12. Bakerydemo's own docker-compose.yml uses postgres 14.1 so I updated this to match.
This will be a breaking change for people with existing installs so I added a make target to remove the pg data volume and documented it in the README.