this post was submitted on 13 Feb 2025
116 points (99.2% liked)
Programming
18180 readers
389 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.