Database migration tool, deduplication of sets data, customizable checkboxes #44

Merged
FrederikBaerentsen merged 51 commits from gregoo/BrickTracker:master into master 2025-01-24 19:12:12 +01:00
Collaborator

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 added 4 commits 2025-01-20 17:50:18 +01:00
gregoo added 27 commits 2025-01-24 10:37:45 +01:00
gregoo added 18 commits 2025-01-24 16:00:34 +01:00
gregoo added 1 commit 2025-01-24 16:05:59 +01:00
gregoo changed title from WIP: Initial work on a database migration tool for incremental upgrades of the schema and data to Initial work on a database migration tool for incremental upgrades of the schema and data 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 checkboxes 2025-01-24 16:07:18 +01:00
Author
Collaborator

@FrederikBaerentsen this could be 1.1.0 unless you want to have your download tool included with it.
I'm currently looking at it.

@FrederikBaerentsen this could be `1.1.0` unless 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:

  • 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
Author
Collaborator

I just realized that it is missing upgrading the version in the compose files and a tag, silly me!

I just realized that it is missing upgrading the version in the compose files and a tag, silly me!
gregoo added 1 commit 2025-01-24 17:57:16 +01:00
Author
Collaborator

I don't have anything else to add to this merge request 😂

I don't have anything else to add to this merge request 😂

Sounds good! I'll go ahead and merge.

Sounds good! I'll go ahead and merge.
FrederikBaerentsen merged commit d2fa72dc63 into master 2025-01-24 19:12:12 +01:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#44
No description provided.