The morning of , after reading a few toots suggesting that the federation of Gitea instances is not relegated to a Utopian future, I impulsively decided to self-host my own git forge.
If you just want to read about giTMI, please jump to the Log.
Why
Why should anyone consider moving out of the great-looking, appealing and feature-packed GitHub, and deciding instead to switch to any of its less diffused alternatives, or even self-host one?
- First, why not? Self-hosting an instance is a nice experiment to try, in my case to test skills, discover new things, and learn more about practically working with open source
- GitHub is centralized, meaning that either you have a GitHub account or you cannot open PRs, issues, etc.
- GitHub is becoming more and more a monopoly, specially since its acquisition by Microsoft
- As far as I know, GitHub is made to host open source software but its own source is not open! This is paradoxical and comically absurd!
- This is not so relevant, but GitHub is written in Ruby, while Gitea is written in Go; this makes Gitea rely on a more modern, faster language and a newer framework.
- If you have more arguments to suggest, please get in touch, I will be happy to add what you write to this list
Log
A schematic log of what I am doing, setting up and maintaining giTMI
- Finding out that forges’ federation is actually going to happen
- Impulsively getting .dev domain
- Installing Gitea on Xplosion Server
- Downloading and using GitTouch as a mobile client
- Solving connection issues via client CLI by editing the
- : finally effectively configured everything
- : migrating to Forgejo
- : As part of my Rethinking tommi.space, I am discontinuing giTMI. I am not happy to do this, but I have to be honest in sharing that I am relieved I have one less technical thing to worry about.
Resources
A collection of inspiring and/or useful articles
config
The configuration file is in /etc/yunohost/apps/forgejo/conf/app.ini.
