Beehaw Support

2795 readers

1 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 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

[–] lemmyng@beehaw.org 18 points 1 year ago

Would it be worth adding a CDN (eg cloudflare or fastly) as a preventative measure? I don't know what your traffic distribution is between static and dynamic content, but i imagine being able to offload image GETs would at least prevent you from getting surprise egress traffic bills.

CF also has an "always online" feature to serve a cached version of the site of the server is down. It won't allow people to post it comment, but it might provide a smoother user experience.