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

document @SHELL feature, allow "info" for all,

Browse source 
...but still distinguish shell folks with a small extra line telling
them they have shell access
This commit is contained in:
Sitaram Chamarty 2009-12-23 19:56:53 +05:30
parent 9c3abb20e1
commit b0ce84d47f
3 changed files with 33 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/6-ssh-troubleshooting.mkd
View file

@ -1,5 +1,20 @@
# ssh troubleshooting
Update 2009-12-23: most of this document is now of historical interest and
will be totally revamped when I have time. For now, just note this amendment.
The document below says "we can't use the same key for both [gitolite access
and shell access]...". We've managed (thanks to an idea from Jesse Keating)
to get around this. Now it *is* possible for a single key to allow both
gitolite access *and* shell access.
This is done by placing such a user in a special `@SHELL` group in the
gitolite config file. As usual, please see `conf/example.conf` for more info
on this, since I'm using that as a central place to document anything
concerned with the conf file.
----
Ssh has always been the biggest troublespot in all this. While gitolite makes
it as easy as possible, you might still run into trouble sometimes.