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

minor doc clarification on easy-install requiring 2 keys for the admin

Browse source
This commit is contained in:
Sitaram Chamarty 2010-10-17 05:10:32 +05:30
parent d1515ea8d8
commit 87cf2d4892
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/1-INSTALL.mkd
View file

@ -219,12 +219,16 @@ server so that if you screw up the keys you can still get on, or be able to
The advantage of this method is that it forces you to solve the ssh pubkey
problem **before** attempting to install. It works best if you have dedicated
userids, one on the server for installing gitolite, and one the client for
userids, one on the server for installing gitolite, and one on the client for
administering it.
Sadly, it also forces the admin to use a different URL to access gitolite
repos than normal users, which seems to confuse a heck of a lot of people who
don't read the prominently displayed messages and/or the documentation.
The disadvantage is that the admin user ends up with [two keys][twokeys] --
one for shell access (that he started with) and one for gitolite access (which
the script creates if needed).
This in turn forces the admin to use a different URL to access gitolite repos
than normal users, which seems to confuse a heck of a lot of people who don't
read the prominently displayed messages and/or the documentation.
This method is verbosely documented in this [transcript][], including
*outputs* of the commands concerned.