Conversation

Notices

1. voltrina voltshenko (voltrina@pl.voltrina.net)'s status on Thursday, 23-May-2024 18:47:17 JST voltrina voltshenko
   given my current circumstances with hosting and being stuck on a practically abandoned pleroma fork, i might migrate to den.raccoon.quest
   
   i wish that there would be proper misskey mobile clients and that the web UI wouldn't use so much battery though
   • iced quinnsmas :blobcatsanta: (icedquinn@blob.cat)'s status on Thursday, 23-May-2024 18:47:13 JST iced quinnsmas :blobcatsanta:

     in reply to

     • Proud owner of a potato sack :flag:
     • Angry Sun
     • Jake (formerly sjw) :lain_sneed:
     • pistolero
     @voltrina i think you have to specifically ping them but one of them might be bored enough
     
     @sun @p @j @hj
     
     i don't remember if lain still does any of this.
   • voltrina voltshenko (voltrina@pl.voltrina.net)'s status on Thursday, 23-May-2024 18:47:14 JST voltrina voltshenko

     in reply to

     • iced quinnsmas :blobcatsanta:
     i hope so, i'll reconsider my decision if someone pops up here
     
     i have switched between *oma forks multiple times in the past without rolling back database migrations on my old instance, but it eventually caused the instance to break as soon as i had to install a update that required database migrations
   • iced quinnsmas :blobcatsanta: (icedquinn@blob.cat)'s status on Thursday, 23-May-2024 18:47:16 JST iced quinnsmas :blobcatsanta:

     in reply to
     @voltrina you might be able to get an adminblob to help you migrate to akkoma or mainline pleroma maybe?
   • pistolero (p@fsebugoutzone.org)'s status on Thursday, 23-May-2024 18:47:56 JST pistolero

     in reply to

     • Proud owner of a potato sack :flag:
     • iced quinnsmas :blobcatsanta:
     • Angry Sun
     • Jake (formerly sjw) :lain_sneed:
     @icedquinn @voltrina @hj @j @sun
     
     > i think you have to specifically ping them
     
     In my case, yes.
     
     > switched between *oma forks multiple times in the past without rolling back database migrations
     
     Just switching FSE from develop to stable required me to jump through some DB migration hoops.
     
     I don't know that you can jump databases from soybox to Pleroma directly: there are gonna be dups that are named differently, there are going to be other conflicts. Usually, the easiest way to do this is hop domains, but the "correct" way to do it would be to revert all of the migrations that happened before the fork, then switch codebases, then run the new migrations. In theory, they'll all apply cleanly, but it is often not the case, since the older databases tend to be the bigger ones and this means they're much harder to test. (FSE's 500 gigs, there are migrations that would take actual days.)