Beehaw Support

2797 readers

34 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 2 years ago

MODERATORS

Penguincoder@beehaw.org

remington@beehaw.org

187

update: Beehaw's update downtime was actually just now. oops. (beehaw.org)

submitted 1 year ago* (last edited 1 year ago) by alyaza@beehaw.org to c/support@beehaw.org

52 comments fedilink hide all child comments

we accidentally did the upgrade just now, which is what you just experienced. anyways we're at like double the power and processing, and three times the storage we were previously at so yeah hopefully that'll be good. anyways i guess i'll leave this post stickied until i go to sleep in like an hour

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

[–] darkfoe@lemmy.serverfail.party 17 points 1 year ago

I'm primarily watching from the sidelines and able to test things if needed for you guys, but I can definitely say this sudden influx is such a rare opportunity for us tech folks (SWEs and sysadmins) to get a real look at what breaks when you do a real load/soak test of a service.

Post-mortems are amazing for tech knowledge, so seeing it kind of "live" is even better.

Good job folks!