deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

(minor) doc updates

Browse source 
inspired by various denizens of #git and the internet at large
This commit is contained in:
Sitaram Chamarty 2010-09-20 23:18:28 +05:30
parent 3f57f18ee2
commit c18514e213
2 changed files with 20 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/2-admin.mkd
View file

@ -140,15 +140,22 @@ for the special usernames or remove the description line.
#### custom hooks #### custom hooks
You can supply your own, custom, hook scripts if you wish. Just put a You can supply your own, custom, hook scripts if you wish. Install gitolite
**tested** hook script in `hooks/common` of your gitolite clone (as as usual, then:
distributed, there are only two files there). For each file in that
directory, a symlink pointing to it will be placed in the `hooks/`
subdirectory of every *new* repo created.
If you added any new hooks and wish to propagate them to *existing* repos as * if you installed using "from-client" method (gl-easy-install):
well, just run gl-easy-install (or gl-setup, if you installed directly on the * go to the gitolite *source* clone from which you did the original
server) once. install
* add your new hook into "hooks/common"
* run src/gl-easy-install with the same arguments as you ran the first
time
* if you installed using one of the other methods
* go to ~/.gitolite/hooks/common on the server and put your new hook
there
* now run "gl-setup" again
You can use this procedure to install new hooks as well as to update hooks
that you had previously installed.
**VERY IMPORTANT SECURITY NOTE: the `update` hook in `hooks/common` is what **VERY IMPORTANT SECURITY NOTE: the `update` hook in `hooks/common` is what
implements all the branch-level permissions in gitolite. If you fiddle with implements all the branch-level permissions in gitolite. If you fiddle with

5
doc/install-transcript.mkd
View file

@ -85,6 +85,11 @@ because I'm not showing the actual "vi" session):
Stopping sshd: [ OK ] Stopping sshd: [ OK ]
Starting sshd: [ OK ] Starting sshd: [ OK ]
**NOTE**: if the `AllowUsers` setting is completely missing from the sshd
config file, all users are allowed (see `man sshd_config`). You may prefer to
leave it that way -- your choice. I prefer to make the usernames explicit
because I'm paranoid ;-)
---- ----
<a name="_get_pubkey_access_from_client_to_server"></a> <a name="_get_pubkey_access_from_client_to_server"></a>