Hosting Git Repositories#

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

install/setup#

If you're installing via your package manager, make sureyou get the right one; it's often calledgitolite3.

Source code is athttps://codeberg.org/sitaramc/gitolite.

If your Unix-fu and ssh-fu are good, take a look at thequick installpage. Otherwise follow the documentation flow, skipping whatever you thinkyou don't need.

documentation#

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

In general, the sections (see links in the navigation bar at the top) shouldbe fairly self-explanatory, and reading through the documentation as it flows(i.e., using the "Next" link at the top right of each page) should work fine.There are some forward references here and there, but you can ignore thoselinks on a first pass.

TROUBLESHOOTING#

Theemergencies page helps with all sorts of install/setup issues,recovering from lost keys and other self-inflicted wounds, lists some common(and some uncommon!) errors and non-standard configs that may trip you up.

contact/support#

security issues#

If you think you found a possiblesecurity issue, please email me(sitaramc@gmail.com) directly.

mailing list(s)#

For all other communications, please use the mailing list. This has someadvantages over sending direct to me (if I'm not available, someone else mightrespond; someone else may have additional info that I may not have thought of,or experiences to share; the issue becomes searchable for future reference;and finally, it keeps me honest!)

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.

Mailing list for support and general discussion:

• Subscribe:gitolite+subscribe@googlegroups.com
• Post:gitolite@googlegroups.com

(If you're unwilling to join the mailing list, you can still send me directmail if it's something simple, obvious, or quick. But if the issue needsmultiple mails and/or some discussion, I prefer the mailing list.)

There's also a low traffic, one-way, mailing list for release and securityannouncements:

• Subscribe:gitolite-announce+subscribe@googlegroups.com

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

IRC#

Our IRC channel is#gitolite on libera.chat. I live in India (UTC+0530 timezone), 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 towait a while for an answer, depending on the time of day and day of week.

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

license#

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

Thisdocumentation, which is maintained separately from the main gitolitesource code, is copyright Sitaram Chamarty and is provided under aCreativeCommons Attribution-NonCommercial-ShareAlike 3.0 UnportedLicense.

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

Documentation for a software product will naturally contain code examples. Ibelieve that the principle of fair use should cover use of those snippets; seeespecially factors 3 and 4 in the list of factorshere.

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