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

warnings on non-root method were not scary enough

Browse source 
(plus some other minor ssh/install related doc enhancements)
This commit is contained in:
Sitaram Chamarty 2011-02-03 19:47:11 +05:30
parent a1cbcf2001
commit 86206641c8
2 changed files with 12 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/1-INSTALL.mkd
View file

@ -234,10 +234,11 @@ we mean `conf/gitolite.conf` on your gitolite-admin clone.
#### (non-root method) directly on the server, manually, without root access
WARNING: if you use this method you'd better know enough about ssh to be able
to keep your keys straight, and you'd also better have password access to the
server so that if you screw up the keys you can still get on, or be able to
"su - git" from some other user on the server.
**WARNING: if you want to use this method your shell access to the git account
on the server should be via `su - git` from some other userid. If that is not
possible, you should (a) know the password in case you screw up the keys AND
(b) know how to force ssh to ask for a password if required, AND (c) know how
to handle multiple keys in ssh.**
* from your workstation, copy your `~/.ssh/id_rsa.pub` file to the server.
Put it in `/tmp/YourName.pub`.

12
doc/ssh-troubleshooting.mkd
View file

@ -38,18 +38,20 @@ code, and documentation.**
Other resources:
* people who think this is too hard should take a look at this
[transcript][] to **see how simple it *actually* is**.
[transcript][] to **see how simple it *actually* is**. This transcript
uses the 'from-client' method of install.
* someone also wrote a tutorial, see [here][tut].
* someone also wrote a tutorial, see [here][tut]. This uses the 'non-root'
method of install, to provide a different perspective.
* I **strongly** recommend reading [doc/gitolite-and-ssh.mkd][doc9gas],
which is a very detailed look at how gitolite uses ssh's features on the
server side. Most people don't know ssh as well as they *think* they do;
even if you don't have any problems right now, it's worth skimming over.
* there's a program called `sshkeys-lint` that you can run on your client.
Run it without arguments to get help on how to run it and what inputs it
needs.
* there's a program called `sshkeys-lint` that you can run on your client to
figure out which key is doing what. Run it without arguments to get help
on how to run it and what inputs it needs.
----