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

(minor doc clarification)

Browse source 
thanks to kfogel for pointing it out
This commit is contained in:
Sitaram Chamarty 2011-03-09 21:40:00 +05:30
parent 396c23e187
commit b0f8924f80
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/2-admin.mkd
View file

@ -23,10 +23,12 @@ In this document:
### please read this first
Unless you know what you're doing, do not do **anything** manually on the
server, like adding new repositories or users or changing the access control
rules. Things will break. For example, if you manually create a repo on the
server, it will not have the required "update" hook, without which there is no
access control for pushes.
server (except when the documentation says you should, for example to add
custom hooks). In particular, adding new repositories or users or changing
the access control rules should not be done directly on the server. Things
will break. For example, if you manually create a repo on the server, it will
not have the required "update" hook, without which there is no access control
for pushes.
Most normal (day-to-day) gitolite admin work is done by cloning the
gitolite-admin repo from the server to your workstation, making changes to the