Adapt some migrations so they can be rolled back #565
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#565
Loading…
Reference in a new issue
No description provided.
Delete branch "ilja/akkoma:fix_some_migrations_for_rollback"
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 may be useful for people who want to migrate back to Pleroma. It's also added in the docs, but also noted that this is barely tested and to be used at their own risk.
I added this because I've seen two cases of people wanting to switch back, plus the website actually says migrations are 100% reversible[1], which wasn't actually true.
I did the rollback on a local dev instance and then did migrations again. Akkoma worked. I did not try an actual migration from Akkoma to Pleroma, but the goal was mostly just to see if the migrations were actually rollbackable without breaking things.
I did the rollback to 20210416051708 because I had it in some notes that this was the last common migration, but I haven't double checked.
Basically, I'm adding it as a way to give people an option, but in the end it's always a risk and it's up to them to decide if the risk and effort is worth it.
[1] https://akkoma.social/
this seems good~
thankies