Beehaw Support

2814 readers

26 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.

if you can see this, it's up

founded 3 years ago

MODERATORS

Penguincoder@beehaw.org

remington@beehaw.org

Beehaws Lemmy upgrade (beehaw.org)

submitted 2 days 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.

you are viewing a single comment's thread
view the rest of the comments

[–] ptz@dubvee.org 18 points 2 days 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 18 points 2 days 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 11 points 2 days 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).