Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features.

Looking for the old "Notes on Git" page? Click here.


Gitolite can be downloaded from git://

If your Unix-fu and ssh-fu are good, installing gitolite is as simple as copying your public key over to the hosting user, and running a couple of commands, as the quick install section of the install page shows.

If you're installing via your package manager, make sure you get the correct version; see the install page for details.


New (April 2014): There's a book on gitolite out. I've received some emails over the years asking where to donate for gitolite to show your appreciation, and I've always refused politely. Well, if you insist... buy the book :-)

Gitolite has a lot of features, and consequently a lot of documentation.

This page (the one you're reading) is the main page. It, as well as most other pages, should have a "Gitolite table of contents" along the right margin (possibly preceded by a "Page table of contents").

If you're not sure where to start, read the main page and the overview page, then look over the rest of the table of contents to decide.

In addition, there's an all-in-one page, with topics in the same order as the main table of contents that you see on other pages. If you want to search for something but don't know which page you saw it, load this and use your browser's find function to search.

(reading order and forward references)

I've tried hard to make the documentation readable in a straight sequence, using the "Gitolite TOC" on the right side. Of course there are places where I have no choice but to refer or link to something that has not been encountered yet, but generally you can ignore those links on a first pass through the documentation.


If you're having trouble, please try the following resources first:

contact and support


Unless you're reporting what you think is a security issue, please use the mailing list for all communication. (NOTE: The first email from a new member is held until I can clear it; subsequent emails from the same email address do not get held up).

If you don't want to participate in the discussions and only want to be informed of releases, security announcements, etc., you can subscribe to the announce list. This is a one-way list; only I can post to it.

If you think you found a security issue, please email me directly: or

If you wish to send me code, please see the file called CONTRIBUTING in the source distribution.


We're on irc at #gitolite on freenode. I live in India (UTC+0530 time zone), but there are a few regulars (thanks, guys, you know who you are!) from other times zones. That said, it's not heavy traffic and you may have to wait a while for an answer, depending on the time of day and day of week.

There are also a few gitolite-knowledgeable people on the git channel #git.


The gitolite software is copyright Sitaram Chamarty and is licensed under the GPL v2; please see the file called COPYING in the source distribution.

This documentation, which is maintained separately from the main gitolite source code, is copyright Sitaram Chamarty and is provided under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.

However, certain parts are contributed by others who may have chosen other licenses; their names and license will be mentioned in the respective files.

Documentation for a software product will naturally contain code examples. I believe that the principle of fair use should cover use of those snippets; see especially factors 3 and 4 in the list of factors here.

If you're not convinced that it would be fair use, then you may consider those code snippets, as well as associated "comments" if any, to be under the GPLv2 license. Licensing is about intent, and the intent of these examples is that you use them wherever and however you can use gitolite itself.

NOTE: GIT is a trademark of Software Freedom Conservancy and my use of "Gitolite" is under license.