When comparing Gogs vs Gitblit, the Slant community recommends Gogs for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gogs is ranked 2nd while Gitblit is ranked 9th.
Ranked in these QuestionsQuestion Ranking
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.
Gitblit is available for Windows, OS X and Linux.
Pro Just works
Setting up is easy and usage is intuitive.
Pro Free and open source
GitBlit is free and open source (under Apache License) .
Pro Built-in authorization in windows
So you don't have to worry about setting up OpenSSH on Windows.
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.
Con No project admins
There's no separation between a system admin and a project admin. There's owners for projects, but to create a new repository one has to be a general admin.
Con Access controls are repository-based
Built in access controls are not branch-based.