Conversation

Notices

1. shitpisscum :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Friday, 17-Mar-2023 16:16:22 JST shitpisscum :verified:

   • 
   @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 :dogsexvomitcube: :SSBBW:
   
   btw @mint I found a screenshot of that "bricking Pleroma by updating" thing I mentioned some time ago, any idea how to prevent this when updating from 2.4.3 to 2.5.0 or whatever's the latest OTP release?
   •  (mint@ryona.agency)'s status on Friday, 17-Mar-2023 16:16:20 JST 

     in reply to
     @shitpisscum @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 Just download the new release, stop pleroma, rename your current directory into something else, unpack the release and rename it into initial directory name, go into that directory and migrate the DB (./bin/pleroma_ctl migrate).
   •  (mint@ryona.agency)'s status on Saturday, 18-Mar-2023 04:21:05 JST 

     in reply to
     @shitpisscum @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 Yeah, looks fine.
     >Also if it shits itself again just removing /opt/pleroma and renaming /opt/pleroma.old
     Not if you migrated the DB already. Gotta have a backup on hand.
   • shitpisscum :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Saturday, 18-Mar-2023 04:21:06 JST shitpisscum :verified:

     in reply to

     • 
     @mint @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 Ok I was looking at the original thread, this appears to to basically the same thing? Or is there something else I might be missing? Also if it shits itself again just removing /opt/pleroma and renaming /opt/pleroma.old to /opt/pleroma should get 2.4.3 running again, right?
     
     Also here's the whole thing if you're curious https://bae.st/notice/ABpibsP5qJu3AXjZ1E
   •  (mint@ryona.agency)'s status on Saturday, 18-Mar-2023 04:21:41 JST 

     in reply to
     @shitpisscum @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 favicon.png should be in the static dir outside of /opt/pleroma to begin with.
   • shitpisscum :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Saturday, 18-Mar-2023 04:21:43 JST shitpisscum :verified:

     in reply to

     • 
     @mint @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 Also this, do I delete favicon.png first just in case? As you can see on the screenshit it does shit itself exactly on favicon.png
   •  (mint@ryona.agency)'s status on Saturday, 18-Mar-2023 04:27:31 JST 

     in reply to
     @shitpisscum @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18 >With that fucked up index that's 2 days downtime, got it.
     Do it now, it won't hurt.
     >So, do I delete it or is my install somehow permanently fucked by that favicon lol?
     It's just a favicon, shouldn't do anything bad to the rest of installation. Probably wrong permissions or something.
   • shitpisscum :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Saturday, 18-Mar-2023 04:27:32 JST shitpisscum :verified:

     in reply to

     • 
     @mint @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18
     >Gotta have a backup on hand
     With that fucked up index that's 2 days downtime, got it.
     
     >favicon.png should be in the static dir outside of /opt/pleroma to begin with
     So, do I delete it or is my install somehow permanently fucked by that favicon lol?
   • shitpisscum :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Saturday, 18-Mar-2023 04:31:17 JST shitpisscum :verified:

     in reply to

     • 
     @mint @e810fafa1e89cdf80cced8e013938e87e21b699b24c8570537be92aec4b12c18
     >Do it now
     Yea might restore another db, call it pleroma2 or something, to have as a "hot spare" lol
     
     Anyway, I might fuck with it this weekend if I have enough time, will let you know if/when I fuck something up
      likes this.