Codeberg AnnouncementsNov 18

Hey everyone! Codeberg will go down for about 10 minutes starting 19.00 UTC (20.00 CET) to create database indices which are expected to improve performance. This requires a short interruption of service.

We apologize for the inconvenience and short notice.

Show threadCodeberg AnnouncementsNov 18
Unfortunately, we are still struggling with the changes. We had unexpected issues with our database cluster, because synchronizing the indexes across nodes failed. However, we are approaching the finish line.
Show threadCodeberg AnnouncementsNov 18

Quick FYI: Codeberg.org has been operational since at least 20:23 UTC (21:23 CET), but our super-duper highly appreciated system administrators grew a bit too tired after dealing with the situation described above, so another social media manager is sharing this one.

This process was a little bit more adventurous ✨ than anticipated, but we believe it was worth the trouble.

Wishing you all a pleasant evening! :)

GustedNov 18
Show threadCodeberg Announcements
(We saw what was happening on the rest of the internet today, and you know that we just had to join in the fun! /joke)
Nov 18 at 9:22pmWeb
Show threadStuart Longland (VK4MSL)Nov 18

@Codeberg Gotta be better than my migration of a PostgreSQL database for a Gitea instance…

Thought I had a full back-up… found out I didn't after I had nuked the cluster. It's been down ever since.

I'm debating whether I dig up my back-up (nothing much would have changed) or whether I just get Forgego going on there instead. I'm in no hurry… it was Anthropic's ClaudeBot scraping the web UI (for a Linux kernel mirror… of all things, drawing ~20W of power and triggering a high-temp alarm in the process) that triggered the whole disaster in any case.