When comparing Gogs vs Gitea, the Slant community recommends Gitea for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gitea is ranked 2nd while Gogs is ranked 3rd. The most important reason people chose Gitea is:
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Self-hosted
Pro Very light
Gogs is very light and has very low minimal requirements.
Pro Excellent performance and efficiency
The fact that it's written in Go means that it has excellent performance even with little resources (less RAM for example).
Pro Simple installation
The installation process is very simple, just a binary file that needs to be run on the directory where the user wants to install Gogs
Pro Open Source
Distributed under the MIT license.
Pro Cross-platform compatibility
Gogs is written in Go, this means that Gogs can be run anywhere that Go can compile. Be it Linux, Windows or OSX.
Pro Light-weight
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Pro Open source and maintained by community
Unlike Gogs, which is maintained primarily by its creator.
Pro Intuitive interface
Easy to navigate around and feels very natural in general.
Pro Non-memory consuming
Just like Gogs, but with new features and fixed bugs. Unlike GitLab which is enormous.
Pro Wiki and issues
Like GitHub, a wiki and issues (bugtracking) can be added to a repository.
Pro Fast pace of development
New features, constantly updated.
Pro Like Gogs but with faster bug fixes
If you love Gogs but were frustrated with the long wait for bugs to be fixed, this is for you.
Pro Most common platforms
Versions available for Linux, Mac and Windows. This is possible because Gitea is developed in the Go language which makes it compact and fast too. Only one executable is needed.
Pro Easy install with MariaDB back-end
No problems getting to work with MariaDB.
Pro Simple to install/written in GO
Pro Package Registry
Supports NuGet, npm, Cargo, Composer, Maven, RubyGems etc.
To work with the NuGet package registry, you can use command-line interface tools as well as NuGet features in various IDEs like Visual Studio.
Pro Runs perfect on a Raspberry Pi 3
Thanks to its light-weight and simple integration.
Pro Customizable Templates
All templates can be overridden.
Pro Focus only on key features
And if you want extra features, you can use web hooks.
Cons
Con Only one maintainer
The project is driven by only one maintainer. The development will stop if he for some reason stops supporting the project.
Con Can not make pull requests between branches of forked repositories
Con No third party provider support
Con Can't filter by a user to see all their commits in one place
I want to see a single user's entire history, but clicking a user's name only shows all users' history, not just the one I clicked.
Con Supports only git
Gogs supports only the Git management system.