The morning of , after reading a few toots suggesting that the federation of Gitea instances is not relegated to a Utopian future, I decided to finally self-host my own git forge.

If you just want to read about GiTMI, please jump to the Log.


First of all, why should anyone consider to move 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 of all, 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 (arguably the fastest) language and a newer framework.
  • If you have more arguments to suggest, please comment below, I will be happy to add what you write to this list


A schematic log of what I am doing, setting up and maintaining GiTMI

  1. Finding out that forges’ federation is actually going to happen
  2. Impulsively getting domain
  3. Installing Gitea on Xplosion Server
  4. Downloading and using GitTouch as a mobile client
  5. Solving connection issues via client CLI by editing the


  1. 🚧 Mirror GitHub repositories
  2. 🚧 Migrate GitHub repositories (once federation is fully implemented)
  3. Custom CSS
  4. Discussions instead of issues?


A collection of inspiring and/or useful articles


My Gitea configuration file, located in /opt/gitea/custom/conf/app.ini