This repository was archived by the owner on Jul 20, 2026. It is now read-only.
Migration Configuration and Scripts - #25
Merged
Merged
Conversation
TheRefraction
added
Documentation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I added a way to manage migrations so that version control wouldn't be an issue as we are not working onto a remote database. Please refer to #23 for more information. I also wrote a script
manage(both for Windows and Linux) for convenience. It is pretty easy to use, just run the script with no parameter to have an overview of what's possible.Once this branch is merged onto
dev, please make sure to fetch updates and base your future branches on (at least) that version ofdev.Finally, you might have to remove and deploy your Docker containers as the configuration has changed significantly. That means you'll also have to update your
.envfile using the one provided.env.example.