Difference between revisions of "Gitolite"

From ArchWiki
Jump to: navigation, search
(Configuration)
m (Update installation section)
(5 intermediate revisions by 4 users not shown)
Line 3: Line 3:
  
 
== Installation ==
 
== Installation ==
{{AUR|gitolite-git}} is available in the [[Arch User Repository]].
+
{{AUR|gitolite}} is available in the [[Arch User Repository]].
  
It is also available on [https://github.com/sitaramc/gitolite/tree/master github], where you can find the last update.
+
It is also available on [https://github.com/sitaramc/gitolite/tree/master GitHub], where you can find the lastest update.
  
 
== Configuration ==
 
== Configuration ==
Line 12: Line 12:
 
  # su - git
 
  # su - git
 
  $ gitolite setup -pk id_rsa.pub
 
  $ gitolite setup -pk id_rsa.pub
 +
 +
Add to your work-machine's ~/.ssh/config:
 +
Host server
 +
HostName 192.168.12.2
 +
User git
 +
### IdentityFile specifies the private ssh-key
 +
Identityfile ~/.ssh/id_rsa
 +
  
 
Do NOT add repos or users directly on the server! You MUST manage the server by cloning the special 'gitolite-admin' repo on your workstation:
 
Do NOT add repos or users directly on the server! You MUST manage the server by cloning the special 'gitolite-admin' repo on your workstation:
  $ git clone git@server:gitolite-admin
+
  $ git clone server:gitolite-admin
  
 
== Add users ==
 
== Add users ==
Line 23: Line 31:
 
Copy all these *.pub files to keydir in your gitolite-admin repo clone. You can also organise them into various subdirectories of keydir if you wish, since the entire tree is searched.
 
Copy all these *.pub files to keydir in your gitolite-admin repo clone. You can also organise them into various subdirectories of keydir if you wish, since the entire tree is searched.
  
Edit the config file (conf/gitolite.conf in your admin repo clone). See the gitolite.conf documentation (http://sitaramc.github.com/gitolite/conf.html) for details on what goes in that file, syntax, etc. Just add new repos as needed, and add new users and give them permissions as required. The users names should be exactly the same as their keyfile names, but without the .pub extension
+
Edit the config file (conf/gitolite.conf in your admin repo clone). See the gitolite.conf documentation (http://sitaramc.github.com/gitolite/admin.html#conf) for details on what goes in that file, syntax, etc. Just add new repos as needed, and add new users and give them permissions as required. The users names should be exactly the same as their keyfile names, but without the .pub extension
 
  $ nano conf/gitolite.conf
 
  $ nano conf/gitolite.conf
  
Line 29: Line 37:
 
  git commit -a
 
  git commit -a
 
  git push
 
  git push
 +
 +
== Gitosis-like usernames ==
 +
If you want to distinguish users with the same login (like username@server1, username@server2) you may want to do the following (for gitolite-3.04-1):
 +
 +
* edit /usr/lib/gitolite/triggers/post-compile/ssh-authkeys and replace
 +
$user =~ s/(\@[^.]+)?\.pub$//;    # baz.pub, baz@home.pub -> baz
 +
by
 +
$user =~ s/\.pub$//;              # baz@home.pub -> baz@home
 +
* update authorized_keys file (for example, by pushing into gitolite-admin repo)
  
 
== See also ==
 
== See also ==
 
http://sitaramc.github.com/gitolite/index.html
 
http://sitaramc.github.com/gitolite/index.html

Revision as of 02:58, 23 September 2013

Gitolite allows you to host Git repositories easily and securely.

Installation

gitoliteAUR is available in the Arch User Repository.

It is also available on GitHub, where you can find the lastest update.

Configuration

Add a user

# useradd -m -U -r -s /bin/bash -d /srv/git git
# su - git
$ gitolite setup -pk id_rsa.pub

Add to your work-machine's ~/.ssh/config:

Host server
HostName 192.168.12.2
User git
### IdentityFile specifies the private ssh-key
Identityfile ~/.ssh/id_rsa


Do NOT add repos or users directly on the server! You MUST manage the server by cloning the special 'gitolite-admin' repo on your workstation:

$ git clone server:gitolite-admin

Add users

Ask each user who will get access to send you a public key. On their workstation generate the pair of ssh keys:

$ ssh-keygen

Rename each public key according to the user's name, with a .pub extension, like sitaram.pub or john-smith.pub. You can also use periods and underscores. Have the users send you the keys.

Copy all these *.pub files to keydir in your gitolite-admin repo clone. You can also organise them into various subdirectories of keydir if you wish, since the entire tree is searched.

Edit the config file (conf/gitolite.conf in your admin repo clone). See the gitolite.conf documentation (http://sitaramc.github.com/gitolite/admin.html#conf) for details on what goes in that file, syntax, etc. Just add new repos as needed, and add new users and give them permissions as required. The users names should be exactly the same as their keyfile names, but without the .pub extension

$ nano conf/gitolite.conf

Commit and push the changes them:

git commit -a
git push

Gitosis-like usernames

If you want to distinguish users with the same login (like username@server1, username@server2) you may want to do the following (for gitolite-3.04-1):

  • edit /usr/lib/gitolite/triggers/post-compile/ssh-authkeys and replace
$user =~ s/(\@[^.]+)?\.pub$//;    # baz.pub, baz@home.pub -> baz

by

$user =~ s/\.pub$//;              # baz@home.pub -> baz@home
  • update authorized_keys file (for example, by pushing into gitolite-admin repo)

See also

http://sitaramc.github.com/gitolite/index.html