More thoughts on and progress with Gitea.

This is a draft post. Find out more about what that means. Get in touch if this post could use an improvement.

This is a part of the 100 Days To Offload challenge.

Today, I cleaned up about forty-five repositories from my GitHub. The ones that are left are mostly ones that…

  • have had some sort of community interaction, or,
  • rely on Vercel or Netlify for CI/CD.

Those are about seventeen in number. I think I can get that down in the future. For now, good enough.

Edit (2021/04/15): You don’t need to rely on GitHub’s integration with Netlify or Vercel. Nicholas Danes linked me to an article on how to use Netlify’s CLI to achieve “git push” style deploys while hosting your repositories on a Gitea instance. 🎉

Honestly – I was a bit surprised to find out they have a neat export feature. I was almost convinced they wouldn’t make it easy to do something like this.

Wait, do something like what? Leave them. Yep. This is especially relevant when your parent company decides to go and put themselves in more places and make presentations with Microsoft ♥ Linux. Embrace, extend, and extinguish, folks. I feel great in that I’m doing this at the right time.

Anyway, I spoke about setting up a Gitea server before, and at the same time, being unsure of what direction it would take… well, I think I have more clarity now.

Here’s my transition plan, and I’m glad to report it’s coming along well!

  • ✅ Export data from GitHub.
  • ✅ Backup my local development folder to an external destination.
  • ✅ Clean up unused/old/abandoned repositories from GitHub.
  • ✅ Mirror repositories that have some degree of interest on GitHub to my Gitea. GitHub stays the source of truth for now, while I still retain a publicly accessible copy on my own server should anything untoward happen.
  • ✅ Move active projects and learning projects to Gitea. I usually prefix the latter with with learn-.
  • ⏳ Update the homepage (check my Git server here) to read better for the people coming from a GitHub-only perspective to git. I will try to get a how-to article out if this is something you want to do in a Docker-based environment for your Gitea server.
  • ⏳ Learn how to make (format?) and send patches over email.

That last point should probably have been the first step, but I don’t think I was ever going to get around to it unless I pushed myself a bit ruthlessly. Now I’ve gone and done that, things should happen.

In the end, anyone with an email account should be able to contribute improvements. I want to be a part of that movement.