this post was submitted on 20 May 2025

1 points (100.0% liked)

Beehaw Support

2878 readers

3 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago

MODERATORS

Penguincoder@beehaw.org

Beehaws Lemmy upgrade (beehaw.org)

submitted 11 months ago by Penguincoder@beehaw.org to c/support@beehaw.org

17 comments fedilink hide all child comments

Ladies and gentlemen, Beeple of all creeds; I stand before you today amid a smattering litany of scripts and testing to say this:

Beehaw production (this site) will be going READ-ONLY at 10pm ET today, May 20th.

This is to finalize the data for migration and moving to the new Beehaw instance, which will be on the latest Lemmy release (0.19.9). There will still be some work to be done and quite possibly a few things not set right. But this is the next step in our migration process. https://status.beehaw.org/ will also be down and not reporting for this timeframe.

I expect the migration to be done within 24 hours; testing shows it should be less time ~ 6 hours but this timeframe gives me a bit more leeway to muck around. When the site is back up, you should easily be able to tell. You can also join the discord or matrix chat to talk amongst yourselves and periodic updates on the migration.

Thank you for your patience and understanding.

top 17 comments

sorted by: hot top controversial new old

[–] ptz@dubvee.org 0 points 11 months ago (1 children)

Oh, cool. Good luck!

One thing you may hit with the DB migrations is foreign key constraint errors in the community aggregates table. Or at least I did when I went from 0.18.5 to 0.19.3 (and again from 0.19.3 to 0.19.9). Basically there were community entries in the aggregates table that weren't in the communities table (or vice versa?)

But definitely be prepared to fight the migration scripts. I usually had to run the one(s) that failed, step-by-step, in a transaction and roll them back to figure out what's failing.

And once you're on 0.19.9, you can use Tesseract :P (I've got some nice mod tools you all might like).

[–] Penguincoder@beehaw.org 0 points 11 months ago (1 children)

Yeah, fighting with the DB has been about 70% of the delay in this process already. Other parts were dealing with pictrs and lemmy integration... still some things to be done, but I'm confident the migration will work well enough be have us operational on a newer version.

[–] ptz@dubvee.org 0 points 11 months ago

Yeah. Not sure if you all have a lot of custom stuff going on with pict-rs, but that's the one place I actually didn't run into issues. Mine's fairly simple and the only major thing I did was migrate it from the sled db to Postgres (which has been a HUGE improvement).

[–] ProdigalFrog@slrpnk.net 0 points 11 months ago (1 children)

Best of luck! :D

[–] ninjaphysics@beehaw.org 0 points 11 months ago

Seconded!

[–] Penguincoder@beehaw.org 0 points 11 months ago (2 children)

Ok so, main migration appears to have gone well enough.

PICTRS/media is not loading, in testing it did fine. So now I'll work on troubleshooting that aspect of Beehaw. For the time though, avatars and beehaw images won't be loading. That's expected for the moment,

[–] apotheotic@beehaw.org 0 points 11 months ago (1 children)

Early days but the site seems orders of magnitude more responsive - not sure if its because of the new Lemmy version or because of reduced user activity from the migration but wow it is night and day

[–] Penguincoder@beehaw.org 0 points 11 months ago

I think it's a combination. But kudos to the lemmy devs for improving the responsiveness of the front end for sure. It is a a noticeable improvement.

[–] ptz@dubvee.org 0 points 11 months ago

Congrats!

[–] Blaze@lemmy.dbzer0.com 0 points 11 months ago

Well done !

[–] arsCynic@beehaw.org 0 points 11 months ago

Anyone have a change log?

[–] ranandtoldthat@beehaw.org 0 points 11 months ago

Nice work. Took until about now for me to be able to upvote and post. Solid for a small org like beehaw!

[–] thingsiplay@beehaw.org 0 points 11 months ago

Finally the bug which didn't allow to use the lower-than character < is fixed. Also a nice sideeffect is, the wrong unread-messages counter for my account is gone (2 was the new 0 for me). Both issues are gone. Thank you for the update.

[–] GammaGames@beehaw.org 0 points 11 months ago

🍻🐝

[–] LukeZaz@beehaw.org 0 points 11 months ago (1 children)

Probably worth mentioning here that this upgrade removed my 2FA, so everybody may want to check and reapply theirs. The 2FA support appears to be less awful this time, at least.

[–] Penguincoder@beehaw.org 0 points 11 months ago

Good call-out. 2FA in lemmy was entirely reworked and uses a different hash on the backend, so the migration removed all existing TOTP tokens. You'll need to read initiate the 2FA if you still want it after this upgrade.

[–] comically_cluttered@beehaw.org 0 points 11 months ago

Cool. Now I can finally switch to better/more maintained app than the one I'm currently using.