Self hosting git repos can be super minimal. If you don’t have a lot of users or repos, just use ssh. Hell you can host a repo on a local SMB network share eben.
Reason I went or self-hosting Forgejo is to know it when federation comes along for real.
I’d love being able to federate my self-hosted Forgejo with my friends self-hosted Forgejo servers. https://forgejo.org/2025-01-monthly-update/#federation
If you’re not stuck on git, give fossil a try. It’s a distributed source code version control with an integrated bug tracker, wiki, forum, and more. All that in in one 3 MB sized binary.
It can even mirror to GitHub and export/import git repositories.
Traditional server-based self-hosting will have lower average uptime, will be easier to attack, and will have a much higher chance of disappearing out of nowhere (bus factor event, or for any other reason).
A decentralized or distributed solution would make more sense as a suggestion here. Radicale (this one) is such an effort I’m aware of, although I never tried it myself or take a look at its architecture.
This is a good argument for self-hosting Forgejo (which is quite simple compared to gitlab from what I hear).
But good to see they are standing up to this shit.
Self hosting git repos can be super minimal. If you don’t have a lot of users or repos, just use ssh. Hell you can host a repo on a local SMB network share eben.
Yes it’s trivial to host a repo, and then you have achieved approximately 2% of a forge.
Reason I went or self-hosting Forgejo is to know it when federation comes along for real.
I’d love being able to federate my self-hosted Forgejo with my friends self-hosted Forgejo servers.
https://forgejo.org/2025-01-monthly-update/#federation
I wish I could upvote this a hundred times.
If you’re not stuck on git, give fossil a try. It’s a distributed source code version control with an integrated bug tracker, wiki, forum, and more. All that in in one 3 MB sized binary.
It can even mirror to GitHub and export/import git repositories.
It’s very easy to host yourself.
Traditional server-based self-hosting will have lower average uptime, will be easier to attack, and will have a much higher chance of disappearing out of nowhere (bus factor event, or for any other reason).
A decentralized or distributed solution would make more sense as a suggestion here. Radicale (this one) is such an effort I’m aware of, although I never tried it myself or take a look at its architecture.
So much simpler than gitlab. An executable and a single config file. That’s all there is if you use sqlite as the database.
Gitlab was a farmyard of different things to worry about.