| License | Apache License, version 2.0 |
|---|---|
| Sources | GitHub & GoogleCode |
| Issues | GoogleCode |
| Discussion | Gitblit Group |
| Google+ | Gitblit+ |
| Ohloh |  |
| Donations | If you enjoy Gitblit and want to support its development, please consider making a donation to St. Jude Children's Research Hospital.  |
Gitblit is an open-source, pure Java stack for managing, viewing, and serving Git repositories.
It's designed primarily as a tool for small workgroups who want to host centralized repositories.
You can browse a live demo here hosted on RedHat's OpenShift cloud service.
NOTE:
The demo is a bit unstable due to a bug in JBossAS7/Tomcat when running in LOW_MEMORY mode which OpenShift mandates. RedHat engineers hope to have this issue resolved soon.
Gitblit GO is an integrated, single-stack solution based on Jetty.
You do not need Apache httpd, Perl, Git, or Gitweb. Should you want to use some or all of those, you still can; Gitblit plays nice with the other kids on the block.
This is what you should download if you want to go from zero to Git in less than 5 mins.
All dependencies are bundled.
Gitblit WAR is what you should download if you already have a servlet container available that you wish to use. Jetty 6/7/8 and Tomcat 6/7 are known to work. Generally, any Servlet 2.5 or Servlet 3.0 container should work.
All dependencies are bundled.
Gitblit Express is a prepared distribution for RedHat's OpenShift cloud service.
All dependencies are bundled.
Gitblit can be used as a dumb repository viewer with no administrative controls or user accounts.
Gitblit can be used as a complete Git stack for cloning, pushing, and repository access control.
Gitblit can be used without any other Git tooling (including actual Git) or it can cooperate with your established tools.
Administrators can create and manage all repositories, user accounts, and teams from the Web UI.
Administrators can create and manage all repositories, user accounts, and teams from the JSON RPC interface using the Gitblit Manager or your own custom tooling.
Gitblit includes a backup mechanism (*federation*) which can be used to backup repositories and, optionally, user accounts, team definitions, server settings, & Groovy push hook scripts from your Gitblit instance to another Gitblit instance or to a Gitblit Federation Client. Similarly, you can use the federation mechanism to aggregate individual workspace Gitblit instances to a common, centralized server.
Gitblit requires a Java 6 Runtime Environment (JRE) or a Java 6 Development Kit (JDK).
