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

doc/6: explain that all this is *only* for the admin

Browse source
This commit is contained in:
Sitaram Chamarty 2009-10-30 17:42:26 +05:30
parent 648dce20ec
commit b94ff910d1
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/6-complex-ssh-setups.mkd
View file

@ -11,6 +11,19 @@ In this document:
* sanity checks * sanity checks
* two gitolite servers to manage? * two gitolite servers to manage?
----
> But before we get to all that, let's clarify that all this is applicable
> **only** to the gitolite **admin**. He's the only one who needs both a
> shell and gitolite access, so he has **two** pubkeys in play.
> Normal users have only one pubkey, since they are only allowed to access
> gitolite itself. They do not need to worry about any of this
> `~/.ssh/config` stuff, and their repo urls are very simple, like:
> `git@my.git.server:reponame.git`.
----
### files on client ### files on client
* default keypair; used to get shell access to servers. You would have * default keypair; used to get shell access to servers. You would have