Gitea

Yesterday, GitLab sent an email to all users (and wrote a blog post) telling that they are updating their terms & services (to which you have to agree) to include a new third party service to track and analyze the behavior of their users, so that they better understand how their users interact with GitLab. That understandably created a lot of backlash from users who don't want to get tracked. Sure, GitLab needs a way to see which features get used in which way, but it's probably not necessary to use a third party service to accomplish this task.
If this post is published on my blog, I successfully developed a nice piece of software that allows me to publish from wherever I go to my blog using just a web browser. Even from my smartphone! How this works? Just a small spoiler before I write a more extensive article: It's a form on a page of my blog and some client-side JavaScript that transforms the entries of that form and calls the Gitea API to create a new file.
Hugo is a framework to build static websites. Yesterday I migrated this blog from Ghost - a dynamic NodeJS based CMS - to Hugo, not only to reduce the hardware requirements (a static page uses way less resources), but also to simplify my setup. I already use Hugo for two basic homepages (my personal one and the AndroidPub one), where I don't have that many requirements regarding “blogging”, because I don't use them for blogs.
There are different reasons for why you may want to install your own git server, like downtimes or new telemetry at GitLab. In this article I want to show you the self-hosted alternative Gitea, which you can easily install on a Virtual Private Server (VPS) with Ubuntu or one of many other Linux distributions (maybe at DigitalOcean or Hetzner) or even a small Raspberry Pi. The installation is actually quite simple…
Jan-Lukas Else
20 years old student who writes about everything he cares about.