Gitea version 1.10: Self-host your own Git service
The goal of Gitea is creating simple, fast, painless self-hosted Git services. It is written in Go and was forked from Gogs, a similar open source project, in 2016. Its newest major release just arrived, with some new features and over 150 bug fixes. Why do people turn to self-hosting services? How does Gitea stack up to other providers or Git hosting solutions?
Gitea’s latest major release, version 1.10, arrived on November 14, 2019.
Under the hood, 1.10 brings some breaking changes, security enhancements, a few features, and bug fixes. Read on to find out more about this project and why some people are turning to self-hosting as a solution.
What is Gitea?
Its README states that its goal “is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service“. For developers who do not wish to host on GitHub (or any number of alternatives), they can create their own self-hosted service.
Gitea is written in Go and is open source and free for all under the MIT license. It began in 2016 as a fork from a project called Gogs, which also offers an open source, self-hosted Git service. (See how it differs from Gogs and the reason for its creation in this introductory blog post.)
It offers cross-platform support; if it supports Go, it works with Gitea. This includes Linux, macOS, Windows x86, ARM, amd64, etc.
New users can migrate from GitHub, GitLab, or Gogs straight to Gitea. Since it is so lightweight with small minimal requirements, it can even run on a Raspberry Pi 3.
Though the source language is English, a translation project helps bring it to other countries. You can help improve translations or add a new language and see your contributions in a future update.
Gitea uses Swagger for its API. It supports webhooks for repository events.
Its settings offer a variety of customizable options. Users can adjust their server for both public and private use. Gitea settings can prevent spammers, only allow specific email domains, block certain providers, and more. Users can customize their experience via the
For CI/CD, Gitea provides a list of solutions that can integrate with it.
Take a look at the demo and become familiar with it.
Version 1.10 changes
1.10 merged 322 pull requests.
Some highlights of the newest release include:
- CI/CD tests enforced for a protected branch: Now, branches can be protected from merging until all of its requirements have passed.
- New password hash algorithms added.
- Webhooks can be triggered with a branch filter by specifying a glob pattern.
- Label sets can be specified during repository creation.
- Compare changes side-by-side: Gitea shows image comparisons when making changes.
- Wiki updates and revisions
- Swagger version updated to 0.20.1
- Over 150 bug fixes!
Check out the release notes for all the info on new changes.
Newcomers can either install from binary for the respective platform or ship it with Docker or Vagrant.
Is self-hosting the right choice for you and your needs? Gitea offers a comparison table showing how it ranks compared to other services including GitLab CE and EE, BitBucket, GitHub EE, and RhodeCode CE.
Self-hosting gives users more active control over their data and how it is stored. It avoids service lock-in and puts you in direct control, instead of depending on a third-party’s solution. Especially with the advent of Software-as-a-Service, we often do not consider how many third parties we depend upon.
A Reddit comment by a Gitea maintainer says the project plans to move their repository off of GitHub in the near future.