Conversation

Notices

1. meso (meso@asbestos.cafe)'s status on Thursday, 01-Jun-2023 21:46:14 JST meso

   • :blank:
   @i how do migration rollbacks work? I want to migrate back to Pleroma, not sure how...
   • meso 🇺🇳 (meso@shitposter.club)'s status on Thursday, 01-Jun-2023 21:46:09 JST meso 🇺🇳

     in reply to

     • Alex Gleason
     • :blank:
     @alex @meso @i do you know how I might be able to migrate from Akkoma to Pleroma?
   • Alex Gleason (alex@gleasonator.com)'s status on Thursday, 01-Jun-2023 21:46:10 JST Alex Gleason

     in reply to

     • :blank:
     • meso 🇺🇳
     @meso @meso @i Let me know how I can help you.
   • Alex Gleason (alex@gleasonator.com)'s status on Thursday, 01-Jun-2023 21:46:11 JST Alex Gleason

     in reply to

     • :blank:
     @meso @i >502 Bad Gateway
     
     Uh-oh...
   • meso 🇺🇳 (meso@shitposter.club)'s status on Thursday, 01-Jun-2023 21:46:11 JST meso 🇺🇳

     in reply to

     • Alex Gleason
     • :blank:
     @alex @meso @i im here
   • meso (meso@asbestos.cafe)'s status on Thursday, 01-Jun-2023 21:46:12 JST meso

     in reply to

     • Alex Gleason
     • :blank:
     @i cc @alex
   • meso (meso@asbestos.cafe)'s status on Thursday, 01-Jun-2023 21:46:13 JST meso

     in reply to

     • :blank:
     @i on the IRC someone said that "Afaik, there's no migration path for that."...
   • Alex Gleason (alex@gleasonator.com)'s status on Thursday, 01-Jun-2023 21:46:59 JST Alex Gleason

     in reply to

     • :blank:
     • meso 🇺🇳
     @meso @meso @i I'm not familiar with the specific database migrations Akkoma did. It's usually not considered safe to rollback. Make a backup of your database before you go any further. Also, why?
   • :blank: (i@declin.eu)'s status on Thursday, 01-Jun-2023 22:51:47 JST :blank:

     in reply to
     @meso shut down the instance, take a sql backup, TAKE A SQL BACKUP
     http://www.aktau.be/2014/10/23/pg-dump-and-pigz-easy-rsyncable-backups-with-postgresql/
     
     setup pleroma from source to where you can run mix ecto commands from either akkoma's or pleroma's dir as the akkoma user
     
     and then be prepared to to restore from backup a few times
     in theory it should be enough to `MIX_ENV=prod mix ecto.rollback -n 1` until it works with pleroma again
     
     though it might be best to rename the akkoma migrations a big number and do a `mix ecto.rollback --to somedate` instead
     
     you might have to adjust the database name and stuff like that in the config
     
     as you can see by the thread, no one has done this yet
     
     there's no real reason to revert back, but if you really want to, i could also bother setting up a test instance and actually documenting it
      likes this.