Article 19
Just adding: The performance problem is also worsened by the fact that we are hit with spam waves for several weeks now. Bots create thousands of issues on Codeberg continuously, and although we got...
View ArticleArticle 18
Hi all, our server is currently unreachable, not even via VPN and the network of our provider does not respond to pings, too.Drink something, test your work again, and push it once we're back online 🧉
View ArticleArticle 17
Our provider confirmed the network outage and is still investigating the cause.There might be another short interruption due to maintenance work in order to permanently fix the problem.Thank you for...
View ArticleArticle 16
We are breaking through the spam waves.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...
View ArticleArticle 15
Want to donate some of your free time to #Codeberg? Make sure to have a regular look at our #Contributing issue tracker: https://codeberg.org/Codeberg/Contributing/issues
View ArticleArticle 14
Some folks are organizing a #Codeberg user meetup in #Dusseldorf, Germany on 2023-10-22.Read all about it on our calendar:...
View ArticleArticle 13
Many people in the Codeberg community think that it is very important to read @drewdevault's blog post about the forbidden topics: https://drewdevault.com/2023/09/29/The-forbidden-topics.htmlThe...
View ArticleArticle 12
We're still looking for co-maintainers for our #Weblate instance at Codeberg.Please see https://codeberg.org/Codeberg/Contributing/issues/23
View ArticleArticle 11
We are performing necessary system updates. We expect a brief downtime (maybe up to two minutes) on Codeberg.org and Codeberg Pages. Woodpecker, Weblate will not be affected.
View ArticleArticle 10
A new version of our membership registration form is live. We are now looking for testers.If you are not yet a member of our non-profit Codeberg e.V. yet, consider giving the new form a try now.Join...
View ArticleArticle 9
We are scheduling system upgrades with elevated risk on Sunday, November 12 during about 10 - 23 CET.We expect brief periods of downtime in best case, let's not talk about the worst case 😉
View ArticleArticle 8
Our letter from November is here: https://blog.codeberg.org/letter-from-codeberg-november-2023.htmlIncludes news about #Forgejo, spam, our membership registration form, and code search.Thank you for...
View ArticleArticle 7
Reminder: We are going to have some maintenance downtime today. We are going to keep you updated in the thread.
View ArticleArticle 6
The scheduled downtime will start in about 2 hours (15 CET, 14 UTC).The exact time will vary a little. We hope that the downtime will last between 15 and 30 minutes only.During a test on another server...
View ArticleArticle 5
We are performing the system upgrades now. Codeberg will go down every moment …
View ArticleArticle 4
We are indeed having problems with our networking setup. We are working on a resolution right now.LXC network experts are welcome to ping us :)
View ArticleArticle 3
The situation is resolved, everything is back online.In short: Our firewall rules were conflicting with the container (LXC) setup after the Debian upgrade.We are still investigating the root cause for...
View ArticleArticle 2
If you are contributing to Free and Libre Software (as developer, designer, UI/UX researcher, translator, and other roles included), how much of your time spent in FLOSS do you dedicate to a project in...
View ArticleArticle 1
From our latest #CommunitySpotlight"New to Codeberg":You might know or use inxi to get information about the Linux or BSD system you are running on. And if you want to update inxi now, you can even get...
View ArticleArticle 0
🛎️ Heads up to Forgejo admins: The Forgejo security team discovered a critical security issue affecting #Forgejo, #Gitea and #Gogs. Check out https://forgejo.org/2023-11-release-v1-20-5-1/ to learn...
View Article
