Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.
Forgejo v9.0 is the first version to be released under a copyleft license, after a year of discussions. Among the motivations for this change is the realization that a pattern emerged over the years, exemplified by Redis, CockroachDB, Terraform and many others. They turned proprietary because people chose their own financial gain over the interest of the general public. Forgejo admins no longer have to worry about this sword of Damocles: relicensing it as a proprietary software is not allowed.
The removal of the go-git backend is part of a larger effort to make Forgejo easier to maintain, more robust and even smaller than it already is (~100MB). When presented with go-git as an alternative to Git, a Forgejo admin may overlook that it has less features and a history of corrupting repositories. It would have been possible to work on documentation and new tests to ensure administrators do not run into these pitfalls, but the effort would have been out of proportion compared to the benefits it provides.
The Forgejo localization community was created early 2024 with the ambitious goal of gaining enough momentum to sustain a long term effort. A daunting task considering there are over 5,000 strings to translate, verify and improve. There has been many calls for help in the past and the community keeps growing steadily. Fortunately, the translation hackathon (translathon) organized by Codeberg in October was exceptional. It attracted an unprecedented number of participants who improved or created thousands of translations.
Has anyone have personal experience moving off of gitea and using forgejo
I'd love to do this but it's hard to find any written experiences yet.
Docker Gitea to Docker Forgejo was basically using a different image and pointing it to the existing database. Not sure if and when both will be different enough for that to no longer work. But I also only use it as a docker compose storage repository. No idea about automation etc.
Cool, I will spend time on it. From what I see, v24 is when gitea and forgejo went their own routes.
I don't think I did more than spinning up the Forgejo container. Using the same db container and everything.
Cool, did you use the built-in CI CD before or after the migration. Any trouble there?
No CI CD, sorry. Just like @JASN_DE@lemmy.world I use it purely to store/archive
if i remember correctly, i just replaced gitea with forgejo for image: in my docker-compose, and it just worked
it was a couple of versions back, so i don't know if that still works