Docker: Implement Persistent PSQL Data in Volumes #746
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
kyleecodes
changed the title
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.
Resolves #588
Also resolves issues not published in GitHub, see below.
What changes did you make and why did you make them?
Previously reduced overhead by moving PSQL database into Docker. In this PR, persistent storage is implemented using Docker volumes. This ensures data stays persistent if containers are deleted and for maintainers to not have to populate cloned forks locally when reviewing forked PRs.
Respective docs are updated to reflect the change.
Did you run tests? Share screenshot of results:
How did you find us? (GitHub, Google search, social media, etc.):