Current Release ${project.releaseVersion} (${project.releaseDate})
release notes

License	Apache License 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.

## What is Gitblit? Gitblit is an open-source, pure Java stack for managing, viewing, and serving [Git][git] repositories. It's designed primarily as a tool for small workgroups who want to host centralized repositories. You can browse the [stable demo site](https://demo-gitblit.rhcloud.com) or the [snapshot demo site](https://next-gitblit.rhcloud.com), both are hosted on [RedHat's OpenShift][rhcloud] cloud service. ### GO: Single-Stack Solution *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. ### WAR: For Your Servlet Container *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. ### Express: For the Cloud *Gitblit Express* is a prepared distribution for [RedHat's OpenShift][rhcloud] cloud service. All dependencies are bundled. ### You decide how to use Gitblit 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. ### Easy Remote Management 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](http://code.google.com/p/gitblit/downloads/detail?name=%MANAGER%) or your own custom tooling. ### Integration with Your Infrastructure - Groovy push hook scripts - Pluggable user service mechanism - LDAP authentication with optional LDAP-controlled Team memberships - Redmine authentication - SalesForce.com authentication - Windows authentication - PAM authentication - Custom authentication, authorization, and user management - Rich RSS feeds - JSON-based RPC mechanism - [Java Client RSS/JSON API library](http://code.google.com/p/gitblit/downloads/detail?name=%API%) for custom integration ### Backup Strategy 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](http://code.google.com/p/gitblit/downloads/detail?name=%FEDCLIENT%). Similarly, you can use the federation mechanism to aggregate individual workspace Gitblit instances to a common, centralized server. ### Java Runtime Requirement Gitblit requires a Java 6 Runtime Environment (JRE) or a Java 6 Development Kit (JDK). [jgit]: http://eclipse.org/jgit "Eclipse JGit Site" [git]: http://git-scm.com "Official Git Site" [rhcloud]: https://openshift.redhat.com/app "RedHat OpenShift"