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.
Any idea how forgejo compares to radicle?
I’m trying to decide what to install on my home server. I want something easy to start with but reasonably extensible and federated would be nice
forgejo is like github copy, and is a fork of the relatively known gitea. so far there are no federation features
radicle is something similar, but as I understand, with distributed repo management. I don’t know the implications of this.
radicle also has an own cryptocurrency, and is entangled with web3.
while not all cryptocurrencies are scams, and probably the same applies to web3 projects, almost all of them are either scams, or useless for the purpose of using it as a currency. I don’t know how the radicle currency fares, but it made me distrust them somewhat when they started talking about that in their announcement channel, and the fact that since then the channel did not post much else did not help to gain back this trust
radicle also has an own cryptocurrency, and is entangled with web3.
And that’s where it breaks the rule of “Do One Thing Well”.
And while it’s super popular to spread and consume everything like a big sticky blob - oh hello, systemd - doing many things poorly (yes, we see you, systemd) needs a lot of diplomacy and help from others - hi, Kay - to keep the code flowing. It’s often not worth it, as we’ve seen but don’t want to admit … with systemd.
(if you’ll excuse me, I need to go change the location of the static nic config files and use a reader more complex than ‘.’ because the windows format is way better and I’m old if I think otherwise)
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.
How long does it take for the new features in Forgejo to appear in Codeberg? I suppose it’s possible they’re already there.
Edit: Codeberg is still on v8.0.3-53, but code.forgejo.org is on v9.0.
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.
;Edit: I will probably just try it
For me, it was literally as easy as (this is basically my upgrade process too):
`
systemctl stop gitea.service
cd /home/git/
wget https://codeberg.org/forgejo/forgejo/releases/download/v8.0.3/forgejo-8.0.3-linux-amd64
mv forgejo-* gitea
chmod +x gitea
systemctl start gitea.service
`
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!
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 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?
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…
It’s interesting that Forgejo ran better than Gitea considering it’s a fork.
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.
