When comparing Gogs vs Bonobo Git Server, 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 Bonobo Git Server is ranked 13th.
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.
Bonobo Git Server is an open-source project under MIT License.
Pro Open source
Bonobo Git Server is an open-source project under MIT License. The source code is available on github and is very extensible.
Pro Web User Interface
Manage users and have full control over your repositories with a nice user friendly graphical interface.
Pro Easy administration
Adding Teams and repositories can done from the UI or by editing files. Very easy
Pro Easy setup and installation
Pro Simple to use
Pro Very simple LDAP integration
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.
Runs under IIS on Windows.
Con Inaccurate installation instructions made for a painful and failed installation
Inaccurate installation instructions which did not reflect what was displayed on the screen, despite following the instructions step by step. Is it really so difficult for developers to test their own instructions against a fresh server to see if they work? Two hours down the drain before moving on to another product... Not as advertised :(
Con Only repository mangment
Not a full DevOps solution, like issue tracking, project management, deploy, etc.