Does anyone know if there's an equivalent to "GitLab Components" in Forgejo?

#forgejo #Gitlab #CICD #Devops #Devsecops

Did you know: #Forgejo always announces security updates in advance (usually at least one week beforehand) to give you time to prepare and be ready when the release is published.

Announcements are made via this tracker: https://codeberg.org/forgejo/security-announcements/issues. You can "watch" the repo or subscribe to the RSS feed to stay informed.

security-announcements

Watch this repository or subscribe to the RSS feed to get advance warning of security releases. They will not reveal the details of the vulnerability but allow Forgejo admins to plan ahead and better secure their instance.

Codeberg.org
Why I'm leaving GitHub for Forgejo | Jorijn Schrijvershof

I left GitHub for self-hosted Forgejo on a hardened NUC. The reason is digital sovereignty, not reliability outages. Here's the thinking and the architecture.

Luckily I have a small collection of unused Mac Minis, so one of those will be running Debian and #forgejo soon.

So I'm torn: Forgejo feels better governance-wise, but Gitea feels more practical for my needs today.

#forgejo #gitea

Follow-up on #Forgejo vs #Gitea:

I read more about the split, and I'm still not sure.

I understand the governance concerns around Gitea, and Forgejo’s FOSS/community direction is very appealing.

But #Gitea supports #OpenTofu state, which I need, and I don't think "open source + paid hosting/support" is a bad model. Actually, it can be one of the healthier ways to fund development.

Maintainers should be paid. Good open-source tools need time, money, and boring long-term maintenance.

@elbosso Ich habe seit längerem #Forgejo und bin auf Codeberg migriert.
Just wondering if anyone is planning on forking #gitlab now that they've decided to enshittify themselves. Or should we just move on over to #forgejo?
Forgejo - v15.0.2 Security Release

Forgejo v15.0.1 released Security bug fixes * PR: fix: prevent git write to wiki repo from unauthorized user via git HTTP * PR: fix: prevent LFS authorizatio...

linux-nerds.org