Note: This page has several forward references. However, I didn't want to place it too far down the list, yet at the same time it's too small to split it into two pages.
This page talks about what gitolite looks like to non-admins, and the commands and features available to them.
The most common setup is based on ssh, where your admin asks you to send him your public key, and uses that to setup your access.
Your actual access is either a git command (like
git clone git@server:reponame, or an ssh command (like
ssh git@server info).
Note that you do not get a shell on the server -- the whole point of gitolite is to prevent that!
Note to people who think gitolite requires or can only handle a specific syntax for the URL: Gitolite is designed in such a way that, unless there is an access violation, the client need not even know that something called gitolite is sitting between it and git on the server. In particular, this means any URL syntax listed in 'man git-clone' for ssh and/or http will work. The only things to note are:
infocommand (see below) shows you.
The only command that is always available to every user is the
info command (run
ssh git@host info -h for help), which tells you what version of gitolite and git are on the server, and what repositories you have access to. The list of repos is very useful if you have doubts about the spelling of some new repo that you know was setup.
Gitolite has two kinds of repos. Normal repos are specified by their full names in the config file. "Wildcard" repos are specified by a regex in the config file. Try the
info command and see if it shows any lines that look like regex patterns, (with a "C" permission).
If you see any, it means you are allowed to create brand new repos whose names fit that regex. Normally, you create such repos simply by cloning them or pushing to them -- gitolite automatically creates the repo on the server side. (If your site is different, your admin will tell you).
When you create such a repo, your "ownership" of it (as far as gitolite is concerned) is automatically recorded by gitolite.
The gitolite config may have several permissions lines for your repo, like so:
repo pub/CREATOR/..* C = ...some list of users allowed to create repos... RW+ = CREATOR RW = user1 user2 R = user3
If that's all it had, you really can't do much. Any changes to access must be done by the administrator. (Note that "CREATOR" is a reserved word that gets expanded to your userid in some way, so the admin can literally add just the first three lines, and every user listed in the second line (or every authenticated user, if you specified
@all there) has his own personal repo namespace, starting with
To give some flexibility to users, the admin could add rules like this:
RW = WRITERS R = READERS
(he could also add other roles but then he needs to read the documentation).
Once he does this, you can then use the
perms command (run
ssh git@host perms -h for help) to set permissions for other users by specifying which users are in the list of "READERS", and which in "WRITERS".
If you think of READERS and WRITERS as "roles", it will help. You can't change what access a role has, but you can say which users have that role.
Note: there isn't a way for you to see the actual rule list unless you're given read access to the special 'gitolite-admin' repo. Sorry. The idea is that your admin will tell you what "roles" he added into rules for your repos, and what permissions those roles have.
desc command is extremely simple. Run
ssh git@host desc -h for help.
The main purpose of gitolite is to prevent you from getting a shell. But there are commands that you often need to run on the server (i.e., cannot be done by pushing something to a repo).
To enable this, gitolite allows the admin to setup scripts in a special directory that users can then run. Gitolite comes with a set of working scripts that your admin may install, or may use as a starting point for his own, if he chooses.
Think of these commands as equivalent to those in
You can get a list of available commands by running
ssh git@host help.
"personal" branches are great for environments where developers need to share work but can't directly pull from each other (usually due to either a networking or authentication related reason, both common in corporate setups).
Personal branches exist in a namespace of their own. The syntax is
RW+ personal/USER/ = @userlist
where the "personal" can be anything you like (but cannot be empty), and the "/USER/" part is necessary (including both slashes).
A user "alice" (if she's in the userlist) can then push any branches inside
personal/alice/. Which means she can push
personal/alice/bar, but NOT
(Background: at runtime the "USER" component will be replaced by the name of the invoking user. Access is determined by the right hand side, as usual).
Compared to using arbitrary branch names on the same server, this: