doasu.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
#Forgejo 13.0.4 and 11.0.9 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
Mal ne Frage an die #Codeberg - Experten hier. Das ist eher nicht mein nächster oder vielleicht auch nur übernächstes #Dud - Projekt, aber man kann ja schon mal Infos sammeln :)
Kann ich eine lokale #Forgejo - Instanz aufsetzen die automatisch von Codeberg synced? Also nicht nur den code, sondern auch issues etc.?
Kann man Accounts synchronisieren? So dass man keine zwei Accounts anlegen muss um in meine eigenen Forgejo-Instanz und Codeberg issues anlegen zu können? (quasi federated)?
@markstos @jwildeboer @homelab for me I self host what makes sense to me. I have #nextcloud #immich #forgejo #jellyfin #keycloak #audiobookshelf . my current goal is to have email #ryoms
So I'm trying to use Forgejo Actions. I defined a job to run inside a OCI container that has the build tool I need. The Action to checkout the repository does not work because it expects nodejs to exist in that container? Also can't share the file system between jobs. Also can't install nodejs in that build container because it doesn't include a package manager (which is fine normally).
I've seen some comments that recommend to build and publish a custom container that includes both the tool I need and nodejs, but surely that can't be the solution.
I don't understand how this is supposed to work? If someone knows how this Action system is intended to be used I'd be grateful.
@spazcosoft @vv i know #ziglang is one:
https://codeberg.org/ziglang/zig#strict-no-llm-no-ai-policy
recently found out #forgejo and #keepassxc involve ai in development which infuriates me
Good luck! In the long run, there is only one serious defense against DDoS and other attacks: federation. I’m really looking forward to @forgejo
supporting federation for repository forks and pull requests.
The #Forgejo monthly report for November was just published! ✨ https://forgejo.org/2025-11-monthly-report/
A security release was published for Forgejo v13 and v11 LTS.
There is another way to report accessibility issues that lowers the barrier. User research is still seeking your help.
A lot of work has been done regarding federation, and the Dutch government has expressed interest in Forgejo.
#Forgejo 13.0.3 and 11.0.8 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
So, to my knowledge, there's nothing that does this yet, but it'll be solved in a very fediversey way soonish:
Dear #Forgejo admins and users,
We are launching another series of user research interviews in the next weeks and invite you to participate. The 45-minutes interviews help us a lot to learn about your usage of Forgejo.
Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to learn more and to schedule an appointment.
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: https://codeberg.org/forgejo/discussions/issues/259
#Forgejo 13.0.2 and 11.0.7 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
I've been playing with #forgejo actions all day. A lot of the basics are barely documented or don't exist yet I guess. Plus it's really hard to search for other people doing the same thing. I also haven't managed to get the artifact actions to ever work. Nothing in the logs of the runner, and a negative runtime reported with just a failure and no details in the forgejo UI :/
Dear #Forgejo admins,
Planning to upgrade to Forgejo v13.0 soon? Join our upgrade party and upgrade together, get help from Forgejo contributors, and get to know the community.
Today, 21 October at 16:00 UTC (18:00 CEST). See https://codeberg.org/forgejo/discussions/issues/402 for details.
@forgejo #ForgejoAneksajo is now available based on #Forgejo 13.0.1 too. It's a soft-fork adding git-annex support on top of Forgejo: https://codeberg.org/forgejo-aneksajo/forgejo-aneksajo
Thank you to everyone who is making Forgejo better every day!
#Forgejo 13.0.1 was just released!
We recommend that all installations are upgraded to the latest version. The v13.0.0 release revealed a bug that has been in the codebase for years and caused the corruption of the Forgejo Actions secrets on instances using PostgreSQL.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#Forgejo 13.0.0 was just released!
A new moderation tool is available to report inappropriate user behavior or content that should be looked at by instance administrators. Two factor authentication (TOTP, etc.) can be enforced on the entire instance for all users or instance administrators. Forgejo Actions usability was improved with static checking of workflow files and access to the logs of all run attempts.
Check out the blog post at https://forgejo.org/2025-10-release-v13-0/
Technically, there are alternatives like #Forgejo or #sourcehut, which tend to have most of GitH*b's features, but without the enshittification.
No idea if it'd be worthwhile to use them for Gentoo, though.
I've only used both for personal stuff, with the exception of hosting Forgejo for my group of friends.
I haven't been involved with Gentoo's infrastructure enough to tell :p
The #Forgejo monthly report was published ✨
The Forgejo v13.0 branch has been cut and the release is scheduled for October 16. Please consider testing it out and sharing your feedback to help us improve it. Forgejo Runner v11 has been released and is now licensed under GPLv3+. Improvements were made to the documentation regarding the Runner setup. Work on improving and securing database interaction has begun. There is an ongoing strong enthusiasm for translating Forgejo.
https://forgejo.org/2025-09-monthly-report