DO NOT MERGE: It's just to show you an example of how this could be done.
A first working version of checking the database user version and applying patches incrementally
Some stuff around the configuration variables reworked for clarity and to avoid potentially missing with Flask
~~**DO NOT MERGE**~~: It's just to show you an example of how this could be done.
- A first working version of checking the database user version and applying patches incrementally
- Some stuff around the configuration variables reworked for clarity and to avoid potentially missing with Flask
gregoo
marked the pull request as ready for review 2025-01-24 16:06:41 +01:00
gregoo
changed title from Initial work on a database migration tool for incremental upgrades of the schema and data to Database migration tool, deduplication of sets data, customizable checkboxes2025-01-24 16:07:18 +01:00
I'm thinking this would be good for a 1.1.0 and then instructions download could be 1.2.0, as I would like to improve it a bit.
Then we also don't get a monster release with too many changes 😄
This is still labeled DO NOT MERGE. Is it ready or?
Flow would be like last time:
Merge
Test locally
Write release post
Push new docker image
I'm thinking this would be good for a 1.1.0 and then instructions download could be 1.2.0, as I would like to improve it a bit.
Then we also don't get a monster release with too many changes 😄
This is still labeled `DO NOT MERGE`. Is it ready or?
Flow would be like last time:
- Merge
- Test locally
- Write release post
- Push new docker image
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
DO NOT MERGE: It's just to show you an example of how this could be done.Initial work on a database migration tool for incremental upgrades of the schema and datato Database migration tool, deduplication of sets data, customizable checkboxes@FrederikBaerentsen this could be
1.1.0unless you want to have your download tool included with it.I'm currently looking at it.
I'm thinking this would be good for a 1.1.0 and then instructions download could be 1.2.0, as I would like to improve it a bit.
Then we also don't get a monster release with too many changes 😄
This is still labeled
DO NOT MERGE. Is it ready or?Flow would be like last time:
I just realized that it is missing upgrading the version in the compose files and a tag, silly me!
I don't have anything else to add to this merge request 😂
Sounds good! I'll go ahead and merge.