Hi folks, we are sorry, but this downtime could last a moment. It looks like one of our root SSDs failed. While the RAID seems to work, the performance has dropped to a level where the whole service is impacted, and even our shell on that server is near to unresponsive.
#NotOnGitHub: Tell us about your favourite #OpenSource / #FreeSoftware projects that are not available on mainstream platforms, whether on a self-hosted cgit or available as an archive download only.
#Frontend developers around? We'd appreciate a helping hand with improving the Codeberg dark theme (also w.r.t. colour contrast), or even more contributors to Forgejo.
#Forgejo 1.20 is released. While we are porting some Codeberg changes and testing the migration, you can already experience the full potential at https://next.forgejo.org - hosted on Codeberg's infrastructure.
Join with your Codeberg account, let your team test-drive the new features, and report the problems you find before other #Codeberg usres experience them.
#Codeberg would not be here without all the free time volunteers donate to our platform and to upstream projects. However, we can give our project a rocket boost with your help. We have compensated a small share of time for their work in #Forgejo, and we have seen immense progress we would waited long for.
There was a big mistake with package storage. We'll need to take Codeberg down and move some data around. We hope that we do not have inconsistencies. We'll try to keep you updated. Please be patient, thank you for understanding.
Today is a sunny day. What do we do on sunny days? We're using our solar power to set up a new server.
Sadly, servers use a lot of energy, and fiddling with the setup of a new server is thus not the most sustainable thing.
Still, we try to do our best and only rely on directly produced energy until it is shipped to the datacenter (where we can only use green power from the standard grid).
Currently at installing the storage using #Debian 12 and #BTRFS.
In the past days, we have identified and fixed several performance bummers, an internal meeting from our core team yesterday evening defined a roadmap to fix the rest.
To give you an idea: We are hit by extreme spam posts. In the past day, we removed 15% (!) of all Codeberg issues as spam, and we're still not done.
The removal degrades the performance, sometimes resulting in error 500s. Please reload the page in that case. Thank you for your patience.
Because we are tired of our current stability issues just like you, we are scheduling some operations during today's Sunday, 30 July 2023.
There will be scheduled downtimes of about 30 minutes each.
We try to limit the length to not interfere with your workflow too much.
We used the last outage to install some outstanding upgrades and fine-tune some database settings which have been identified in a recent contributor meeting.
Today, we will continue working on our storage … read on
