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.
Was this the git hosting service that wanted to have things like federated (in this case im talking about cross instance) cloning, searching and issue hosting?
I may be mistaken in general but iirc there was a hosting service like this that I found super interesting, especially in light of things like DMCA abuse against projects hosted on github and gitlab.
EDIT: seems like it is one of two, forgefed is a protocol it will use, activitypub one, very interesting.
You do realize git is federated right? That's how it came about.
As for Forgejo itself they are working on instance to instance federation. I think it is Activity pub based so theoretically it could be compatible with Lemmy.
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.
I did it soon after the "split up" though, but it was super easy since they were still basically the same applications.
Make backups, update the above to use your paths and the new download link you should be good to go. Mine is in a VM , so I was willing to just YOLO and give it a go since I could easily roll back.
sorry for the formatting. on my phone and did my best!
Check their website for migration info. There are some caveats in special circumstances but most people can just change the docker image from gitea to forgejo.
Ah, nice. Had been experimenting with using my Raspberry Pi 3B as my home Git server for all my personal projects - easy sync between my laptop and desktop, and another backup for the the stuff that I'd been working on.
Tried running Gitea on it to start with, but it's a bit too heavy for a device like that. Forgejo runs perfectly, and has almost exactly the same, "very Github inspired" interface. Time to run some updates...
Yeah. Doesn't take much optimising of disk writes to make things run much better on a Pi; they're quite capable machines as long as disk i/o isn't your limiting factor. Presumably the devs have been doing some tidying up.
Do you use it for anything other than syncing code? Currently I'm using plain SSH sync for all my personal git repos, and I'm not sure if there'd be any advantage in switching to Forgejo.
My workplace is a strictly BitBucket shop, was interested in expanding my skillset a little, experiment with different workflows. Was using it as a fancy 'todo' list - you can raise tickets in various categories - to remind myself what I was wanting to do next in the game I was writing. It's a bit easier to compare diffs and things in a browser when you've been working on several machines in different libraries than it is in the CLI.
Short answer: bit of timesaving and nice-to-haves, but nothing that you can't do with the command line and ssh. But it's free, so there's no downside.
To be fair, they supported two different git backends, one of them being go-git which was the one corrupting repositories. However, it was never enabled by default, you specifically had to build Forgejo with a specific tag to instead use that as the backend. If you just built normally or pulled ready-made containers or bins then it was always the default git backend.
Forgejo is a free/open source code hosting site like GitHub or Gitlab. It's a fork of Gitea, over concerns with management and commercialization. You might know it from Codeberg, which is one of the largest managed instances, but it's really easy to host your own.
It was new to me too, but a (code) forge is essentially a VCS server with stuff like a wiki and issue tracking. So think GitLab, GoGS/Gitea/Forgejo, BitBucket and all the others.