Api web database migration to PG17 #647
Merged
Conversation
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
Update postgres version
API DB migration to PG17
… bring back ja.
…ation-repairs More work toward https://github.com/OpenHistoricalMap/issues/issues/1…
Set a new EBS for web api - staging Set api_readonly - staging Update EBS id for API web - production Update config ids for EBS - v2
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.
From: OpenHistoricalMap/issues#1136
Work that we done in other repos to make this posible: developmentseed/osm-seed#381, https://github.com/OpenHistoricalMap/ohm-deployment/pull/10