HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sitaramc
gitolite
Perl2010–2023
sitaramc / gitolite

gitolite

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

17Distinct people
20Mentions
0Explicit recommenders
8.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year20 dated mentions

Observed mentions: 2010-02-08 02:15:26 UTC to 2023-05-11 15:08:01 UTC.

02462010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC202
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC707
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC615
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Gitolite README about this README (Github-users: click the "wiki" link before sending me anything via github.) This is a minimal README for gitolite, so you can quickly get started with: installing gitolite on a fresh userid on a Unix(-like) machine, using ssh learning enough to do some basic access control For anything more, you need to look at the complete documentation, at: http://gitolite.com/gitolite. Please go there for what/why/how, concepts, background, troubleshooting, more details on what is covered here, advanced features not covered here, migration from older gitolite, running gitolite over http (rather than ssh), and many more topics. Assumptions You are familiar with: OS: at least one Unix-like OS ssh: ssh, ssh keys, ssh authorized keys file git: basic use of git, bare and non-bare remotes You are setting up a fresh, ssh-based, installation of gitolite on a Unix machine of some sort. You have root access, or someone has created a userid called "git" for you to use and given you a password for it. This is a brand new userid (or you have deleted everything but .bashrc and similar files to make it look like one!) If your server is not connected to the internet, you know how to clone the gitolite source code by using some in-between server or "git bundle". Installation and setup server requirements any unix system sh git 1.6.6 or later perl 5.8.8 or later openssh 5.0 or later a dedicated userid to host the repos (in this document, we assume it is "git", but it can be anything; substitute accordingly) this user id does NOT currently have any ssh pubkey-based access ideally, this user id has shell access ONLY by "su - git" from some other userid on the same server (this ensure minimal confusion for ssh newbies!) steps to install First, prepare the ssh key: login to "git" on the server make sure ~/.ssh/authorized_keys is empty or non-existent make sure your ssh public key from your workstation has been copied as $HOME/YourName.pub Next, install gitolite by running these commands: git clone https://codeberg.org/sitaramc/gitolite # (or) git clone https://github.com/sitaramc/gitolite mkdir -p $HOME/bin gitolite/install -to $HOME/bin Finally, setup gitolite with yourself as the administrator: gitolite setup -pk YourName.pub If the last command doesn't run perhaps "bin" is not in your "PATH". You can either add it, or just run: $HOME/bin/gitolite setup -pk YourName.pub If you get any other errors please refer to the online documentation whose URL was given at the top of this file. adding users and repos Do NOT add new repos or users manually on the server. Gitolite users, repos, and access rules are maintained by making changes to a special repo called "gitolite-admin" and pushing those changes to the server. To administer your gitolite installation, start by doing this on your workstation (if you have not already done so): git clone git@host:gitolite-admin NOTE: if you are asked for a password, something went wrong.. Go hit the link for the complete documentation earlier in this file. Now if you "cd gitolite-admin", you will see two subdirectories in it: "conf" and "keydir". To add new users alice, bob, and carol, obtain their public keys and add them to "keydir" as alice.pub, bob.pub, and carol.pub respectively. To add a new repo "foo" and give different levels of access to these users, edit the file "conf/gitolite.conf" and add lines like this: repo foo RW+ = alice RW = bob R = carol Once you have made these changes, do something like this: git add conf git add keydir git commit -m "added foo, gave access to alice, bob, carol" git push When the push completes, gitolite will add the new users to ~/.ssh/authorized_keys on the server, as well as create a new, empty, repo called "foo". help for your users Once a user has sent you their public key and you have added them as specified above and given them access, you have to tell them what URL to access their repos at. This is usually "git clone git@host:reponame"; see man git-clone for other forms. NOTE: again, if they are asked for a password, something is wrong. If they need to know what repos they have access to, they just have to run "ssh git@host info". access rule examples Gitolite's access rules are very powerful. The simplest use was already shown above. Here is a slightly more detailed example: repo foo RW+ = alice - master = bob - refs/tags/v[0-9] = bob RW = bob RW refs/tags/v[0-9] = carol R = dave Here's what these example rules say: alice can do anything to any branch or tag -- create, push, delete, rewind/overwrite etc. bob can create or fast-forward push any branch whose name does not start with "master" and create any tag whose name does not start with "v"+digit. carol can create tags whose names start with "v"+digit. dave can clone/fetch. Please see the main documentation linked above for all the gory details, as well as more features and examples. groups Gitolite allows you to group users or repos for convenience. Here's an example that creates two groups of users: @staff = alice bob carol @interns = ashok repo secret RW = @staff repo foss RW+ = @staff RW = @interns Group lists accumulate. The following two lines have the same effect as the earlier definition of @staff above: @staff = alice bob @staff = carol You can also use group names in other group names: @all-devs = @staff @interns Finally, @all is a special group name that is often convenient to use if you really mean "all repos" or "all users". commands Users can run certain commands remotely, using ssh. Running ssh git@host help prints a list of available commands. The most commonly used command is "info". All commands respond to a single argument of "-h" with suitable info
Read the full README on GitHub

What Hacker News says

7 sources
If you end up trying to setup git on a linux machine, two things: - setup or have available another linux machine to act as a "client". git on windows with ssh can be a bit fidgety sometimes, and that would help you debug whether it's a client or server issue. - do look at gitolite for managing the repos [1]. Its "simple" to install, and the features it brings to the table are awesome (from private 'scratch' repos to auth and key management, and several others). [1] - https://github.com/sitaramc/gitolite#_quick_install
In Subversion 1.7 is out
The killer feature of codeplane is cheap shared private git repositories. If you are the only person using your git repo, there is no reason you wouldn't store your remote on some random webhost (you can do this at http://nearlyfreespeech.net for essentially free). If you want to collaborate with this setup, you would need to create a system-level account for every collaborator on your VPS (ugly) or install something like gitolite (https://github.com/sitaramc/gitolite). The downside to gitolite is then you are running your own VPS, i.e. are responsible for security, updates, config, etc. It seems codeplane takes care of all the nonsense for you so you can get on with your real project. As someone who had to set up gitolite because of this exact need, I can attest to the need for a service like codeplane.
In Why I've built an alternative to Github
You can set something like this up on any VPS with gitolite (https://github.com/sitaramc/gitolite) pretty easily. gitolite lets you set up very fine-grained per-user/repo/branch permissions, manage your users' SSH keys, and gives you nice clean git@git.you.com:repo-name access to your remotes. I've done this for myself with a $48/year VPS from prgmr.com specifically because I needed more private repos than Github could offer (my setup instructions are here: https://gist.github.com/1035834). Granted, if codeplane.com existed six months ago I probably wouldn't have bothered with gitolite. It appears they do nice things for you like backups.
In Why I've built an alternative to Github
No matter how often you want to review code, I think it could work for your team like this: - dev works on a feature branch, making multiple commits and pushes - once ready, squash all the commits and submit it to gerrit [- perhaps have hudson/jenkins run the unit tests at this point automatically] - have the code review in gerrit - once the review is done, gerrit would merge it into the develop or master branch (depending on your git workflow) That approach blends in nicely with git-flow (1). If you want to be sure that no single dev is pushing to the develop or master branches you'd need to setup per-branch permissions, which can be done with gitolite (2). Too bad github (even the self-hosted version) doesn't support per-branch permissions, which forces organizations that use it and only want gerrit to be able to push into the main bran
Read the rest
ch to do excessive repo forking instead of using feature branches. Also I'd love to be able to do ad-hoc code reviews in github, as the interface is the most beautiful of all imo. [1] http://nvie.com/posts/a-successful-git-branching-model/, https://github.com/nvie/gitflow, http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flo... [2] https://github.com/sitaramc/gitolite
In Rietveld - code review Google style
You can configure git-receive-pack to not allow ref deletes (receive.denyDeletes) or any ref updates which aren't fast-forwards (receive.denyNonFastForwards), which makes this kind of data loss impossible. With Gitolite you can even set this permission per-user per-branch (https://github.com/sitaramc/gitolite#_main_features) so that the great power is only given to those with the great responsibility to handle it. Of course, somebody still has to know and care enough to want to tweak the default configuration, and it doesn't help with GitHub for the moment, but I wouldn't be surprised if they added finer-grained branch permissions in future.
In Mea Culpa: GitHub works well, my mistake made them look bad

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.