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.
2b6472b655to120150558675c530cecbto8e18a11fc85ff906086bto2fcc7ffc5b2fcc7ffc5btob9ff049705b9ff049705to44a7abab8244a7abab82toaeb4c39a12Now based on #24
0b5b73edc3to507eb8d711507eb8d711to8fbdac365f8fbdac365fto50385824065038582406to1ac164b8601ac164b860to573bea2da074ceb1b1f3toe9fbce0da7e9fbce0da7to28800767052880076705toa289664f10a289664f10to74ca9b247d74ca9b247dtoee38e46c12WIP: feature/migrations, closes #19to feature/migrations, closes #19