@p@sjw@1ns0mniak@cope@miklol2@graf@shitpisscum None of that is exclusive to source install, you can easily build OTP packages yourself with whatever changes you want. OTP is just nicely packed, does not require the whole toolchain to be installed to run and also allows for easy access to iEX console.
@p@sjw@1ns0mniak@cope@miklol2@graf@mint Planned to do the update tonight but I'm kind of busy, will probably do it tomorrow or wednesday (why wednesday in particular , well I'll leave it up to you to figure out), but decided to do a quick experiment last night: made another backup of the original db with --quote-all-identifiers and tried restoring it (didn't srop anything, a separate db, literally called it pleroma1 lol). Anyway, it's been stuck on creating INDEX "public.activities_visibility_index" for almost a full day now. Also had the same issue when restoring the current db (the one pleroma's using rn), it also took more than 24 hours to build that index. My question is, is this normal for pleroma's db or does that mean the original db itself is fucked and I'm just restoring a broken backup?
inb4 I told you not to do it in all caps: I didn't drop anything this is a separate db, the old one is still "running"
inb4 update: I will and you will be notified, I'm just asking whether this particular behavior is normal or indicates some additional issues
in4 doxxed you because you're gonna update pleroma on wednesday: :pleromatanshrug: