feature/migrations, closes #19 #20
No reviewers
Labels
No Label
🛃 types
👪 users
invalid
wontfix
🚀 announcement
🎒 backend
🐞 bug
🐋 docker
💡 enhancement
📺 frontend
🤔 question
🔗duplicate
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
#24 feat(plugins): Load metadata from entry points / distribution
Flaschengeist/flaschengeist
Reference: Flaschengeist/flaschengeist#20
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/migrations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is work in progress!
Adding migrations is important, #19, as this allows users to update the database without manual interaction.
TODO:
Some more work is needed, as currently removing / disabling a plugin might break migrations -> can not identifiy which version is the current migration.
Planned workflow:
Every DB change on develop -> new migration file
stable release on main -> merge migrations into one file (cleanup)
So every user on stable can upgrade and downgrade its db and same on develop, but we do not need to provide X migration files for every development step.
So we can clean up at every stable relase, dropping stable migrations is not needed I think, but can be done with some delay.
2b6472b655
to1201505586
75c530cecb
to8e18a11fc8
5ff906086b
to2fcc7ffc5b
2fcc7ffc5b
tob9ff049705
b9ff049705
to44a7abab82
44a7abab82
toaeb4c39a12
Now based on #24
0b5b73edc3
to507eb8d711
507eb8d711
to8fbdac365f
8fbdac365f
to5038582406
5038582406
to1ac164b860
1ac164b860
to573bea2da0
74ceb1b1f3
toe9fbce0da7
e9fbce0da7
to2880076705
2880076705
toa289664f10
a289664f10
to74ca9b247d
74ca9b247d
toee38e46c12
WIP: feature/migrations, closes #19to feature/migrations, closes #19