Alright, it’s been a while since the last blog post. You have probably noticed the blog was updated to use hugo and GitHub pages, since I couldn’t stand the slowness of jekyll and the pain of having to roll out my own system to publish blog posts on my blog. Either way, it works, the old links are kept working, so I’m really happy with the outcome. What I want to talk today is that zxq.co is now a website for git code hosting. Another one. Yes.
I made this decision 2 days ago, seeing as a few people wanted to have some free code hosting and perhaps even help us work on Ripple, which at the time being if you’re not an official developer is only possible through pull requests on the official repos, which are hosted at the former git.zxq.co, while those on GitHub are just mirrors.
So what I also did while migrating git.zxq.co to zxq.co was moving from Gogs to Gitea. Gitea is a fork of Gogs with the basic difference that it’s community-maintained. This basically means that the status of the project doesn’t depend on the main maintainer currently being at home, but rather on the community making pull requests, reporting issues and merging pull requests, which for an open source project this is a much better solution. At the current stage, Gitea already has a pretty much complete API, has reached a stable and frozen 1.0.0, and pull requests are being merged constantly, which makes it more likely to eventually become a private git solution comparable to, say GitLab.
The main reason why I don’t use GitLab is because performance and use of resources, which is also why I’m a fan of Go and most projects and libraries written with it: writing code in Go is fun, and the code you write in it will almost always be very fast and not resource-intensive. Yes, sure, garbage collection takes its toll, but nothing comes close to the amount of stuff needed by programs written in dynamic languages. That’s basically the resume of all the reasons of why I use Go as my main programming language.
So yeah, if you have a gogs instance and haven’t moved to Gitea already, you should definetely do that, and it doesn’t take much to do that. For me, it was
code.gitea.io/gitea, going into the folder,
go build, copying the custom folder, the data folder, and adding the
SSH_DOMAIN setting in the config. After that, everything was good to go.
The only slight criticism I have for Gitea is, well, the logo, which is one of the most horrible things in this world. But well, let’s hope a graphic designer happens to drop his eye on Gitea eventually and give the maintainers a slighlty more decent logo.