Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing GitStack vs Gitblit, the Slant community recommends Gitblit for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gitblit is ranked 10th while GitStack is ranked 13th. The most important reason people chose Gitblit is:
Setting up is easy and usage is intuitive.
Specs
Question Ranking
Pros
Pro Free and open source
GitStack is free and open source. It's source code can be found on GitHub.
Pro FREE Business Edition if you write a blog post about them
They offer a FREE Business Edition if you have a blog and write a post about them. That's $720 you don't have to pay.
Pro Easy setup
There is a wizard setup that installs GitStack on windows in about 3 minutes.
Pro Can manage users and groups out of the box
GitStack supports user and group management and permissions. Different users or groups can have different permissions.
Pro LDAP support
The Lightweight Directory Access Protocol is an application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network.
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 Cross-platform
Gitblit is available for Windows, OS X and Linux.
Pro Built-in authorization in windows
So you don't have to worry about setting up OpenSSH on Windows.
Cons
Con Windows only
Unfortunately GitStack is not cross-platform. It only runs on windows.
Con Does not support issue tracking
There is no issue tracking out of the box for GitStack, companies that choose to use it usually have a issue tracking software already installed and running.
Con Git only
Supports only Git version control system.
Con Clear Port 80
When installing, you must have port 80 clear or it won't install. You can change the port after install, but for install, it must be clear.
Con No code reviews
It's not possible to start any code reviews on Pull Requests
Con Access controls are repository-based
Built in access controls are not branch-based.
Con No Squash Merge
There is no Squash Merge functionality
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.
