Forgejo. It is a fork of Gitea.
this post was submitted on 21 Apr 2025
37 points (100.0% liked)
Programming
19750 readers
62 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
A better* fork of Gitea!
how so? Is it easier to set up or have more features? What's the difference? please educate me :D
Not sure if its better, did both and i havent noticed much difference. Forgejo runs codeberg though and is maintained by them. Also has CI with forgejo actions.
And Gitea has Gitea Actions. The big difference - and also the sole reason ForgeJo was forked - is that Gitea has a business behind it that allows them to sell support hours to other businesses. And then use the money to progress Gitea. Similar to how Zabbix and others do it. But the community decided that this is a bad thing and moved to ForgeJo.
gittea ltd was founded without adhering to the governance model gittea had and also claimed copyright on atleast the name and logo of gittea. many felt a non-profit would be a better way to organize development and thats how codeberg e.v. came to be.
the problem is not, and never was offering support and service against money, you can right now start selling forgejo if you'd desire to, it was allways about how the project itself should be organized.
While a non-profit sounds very honourable, I personally think Gitea has the more future-proof model. In fact, Gitea Actions was something they got commissioned for and were allowed to open source it as well.
This is basically how I think about it. (Not my comment.)
But we’ll see…
how so?
I'd like to get educated as well, please. So far, ForgeJo doesn't seem to have any specific advantage over Gitea. (And the name couldn't be worse...)
what's the difference?
https://forgejo.org/compare-to-gitea/
CI actions and actually being free software are my main notes, but there are many reasons.
wait...how is forgejo developed on forgejo? If there is no forgejo to begin with, how did they begin developing?
edit: maybe they switched from github to forgejo a bit later?
This process is called 'bootstrapping', and is actually quite common in software. For example, the C compiler is written in C. The first iteration of the C compiler was written by hand in assembly code with a very limitted feature set, and that compiler was then used to compile the next iteration, allowing the second version (I'm not sure it was actually the second version; there may have been a few iterations in assembly) to be written in C itself.
For Forgejo, you dont actually need Forgejo to build Forgejo; just a computer with the Go compiler and any other dependencies. Then, once you have the first version, you can publish the code you have on Forgejo. Nothing too crazy there 🙂
This also leads to 'dogfooding', which is a whole other term...
ahh okay :0
ah okay
Since you're a bit concerned about self hosting and collaboration, I would recommend Codeberg - they are a non-profit based in Germany with widespread support and, as far as I know, is the public Forgejo instance with the largest user base.
If you want, you can also host your own Forgejo instance and mirror your Codeberg repos to it. That way you can have two copies of your data, just in case Codeberg ever goes offline.
You could also potentially use Gitlab, but I would personally prefer something Forgejo based. Forgejo has been much more responsive/snappier in my opinion; Forgejo is primarily written in Go, while Gitlab is mostly Ruby.
ah okay I'll try that
There's also an official guide for this: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
However, Codeberg seems to push for excluding proprietary software dependencies, which might limit the kinds of projects I can do.
Well, they ask for software projects to be themselves under a FOSS license. If you can isolate the proprietary dependencies, you could still open-source the code.
Of course, you could also consider using Codeberg for all your open-source projects and then self-host a Git server for your proprietary projects.