There will be several short interruptions in service during the next 24 hours. Each should not last more than a few minutes. We are performing scheduled hardware maintenance, replacing 1 of 3 physical servers. You can find the current status at

Codeberg Service Status

This is an overview of the Codeberg Infrastructure. Uptime stats are calculated over the past 24 hours only. <a href=https://social.anoxinon.de/...

Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load. This is an important milestone, because such a setup was never tested with #Forgejo at this scale. This should improve availability of both Codeberg.org and Codeberg Pages. Details:

Codeberg.org

Clustered Forgejo for Codeberg - Our journey and your knowledge

Hi everyone! At Codeberg, we are currently looking into running multiple Forgejo instances (&#34;clustering&#34; / &#34;high availability&#34;). Be...

We apologize for the long performance degradation today. Finally, we identified all of the 'tricks' that AI crawlers found today. They no longer bypass the anubis proof of work challenges. A novelty for us was that AI crawlers seem to not only crawl URLs that are actually presented to them by our frontend, but they converted the URLs into a format that bypassed our filter rules. By the way, you can track the changes we have been doing via

Cookie monster!

We have upgraded to Forgejo v13. You can read the official announcement for the release here:

Forgejo v13.0 is available

If you have unexpected issues, please don't hesitate to let us know.

Codeberg.org

Community

Discussion of community- and platform-related issues