For now it’s just another process running on my server, but after a journey from public hosted bitbucket over github and gitlab to a selfhosted gitlab I have finally arrived at gitea, and I must say I’m impressed. With my system adminstration hat on I have to admire the ease of both installation (just one binary instead of a multipart multiprocess nearly-containerized blob like gitlab - nothing against gitlab, I still think they have understood devops and gitops better than any of the others) and daily operation (integration with oauth2, just one port to worry about, and it’s up to me how I access it - directly, through nginx or as in my case, apache2’s mod_proxy, which again gives me full freedom to leverage my previous efforts to make SSL work in a just-forget-it setting with the help of letsencrypt).

So, shoutout to the people working on Gitea, Lets encrypt and of course both Linus Torvalds for git and Google for go.

Next is integration with some CI/CD running on my home kubernetes cluster (which I also should describe some time… let me iron out the worst bugs first), I see most people use Drone CI, I have used Jenkins before and know to avoid it, and I think buildbot looks very neat. We’ll see.