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

(minor) more doc updates, really small ones

Browse source
This commit is contained in:
Sitaram Chamarty 2010-12-31 19:51:06 +05:30
parent ffcbc52637
commit e0f4bbaf16
5 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
conf/example.gitolite.rc
View file

@ -1,6 +1,7 @@
# configuration variables for gitolite # configuration variables for gitolite
# PLEASE READ THE DOCUMENTATION BEFORE EDITING OR ASKING QUESTIONS # PLEASE READ THE DOCUMENTATION BEFORE EDITING OR ASKING QUESTIONS
# ( http://github.com/sitaramc/gitolite/blob/pu/doc/gitolite.rc.mkd )
# this file is meant to be pulled into a perl program using "do" or "require". # this file is meant to be pulled into a perl program using "do" or "require".
# You do NOT need to know perl to edit the paths; it should be fairly # You do NOT need to know perl to edit the paths; it should be fairly

2
doc/delegation.mkd
View file

@ -71,7 +71,7 @@ in charge of malware ;-)
[abe]: http://en.wikipedia.org/wiki/Alice_and_Bob#List_of_characters [abe]: http://en.wikipedia.org/wiki/Alice_and_Bob#List_of_characters
You do this by adding branches to the `gitolite-admin` repo: You do this by adding files with specific names to the `gitolite-admin` repo:
# the admin repo access was probably like this to start with: # the admin repo access was probably like this to start with:
repo gitolite-admin repo gitolite-admin

2
doc/install-transcript.mkd
View file

@ -127,7 +127,7 @@ described in the `ssh-copy-id` section in `doc/3-faq-tips-etc.mkd`).
| .. | | .. |
+-----------------+ +-----------------+
sita@sita-lt:~ $ ssh-copy-id -i ~/.ssh/id_rsa git@server sita@sita-lt:~ $ ssh-copy-id -i ~/.ssh/id_rsa.pub git@server
git@server's password: git@server's password:
/usr/bin/xauth: creating new authority file /home/git/.Xauthority /usr/bin/xauth: creating new authority file /home/git/.Xauthority
Now try logging into the machine, with "ssh 'git@server'", and check in: Now try logging into the machine, with "ssh 'git@server'", and check in:

2
doc/progit-article.mkd
View file

@ -24,7 +24,7 @@ We will describe this last method in this article; for the other methods please
You start by obtaining public key based access to your server, so that you can log in from your workstation to the server without getting a password prompt. The following method works on Linux; for other workstation OSs you may have to do this manually. We assume you already had a key pair generated using `ssh-keygen`. You start by obtaining public key based access to your server, so that you can log in from your workstation to the server without getting a password prompt. The following method works on Linux; for other workstation OSs you may have to do this manually. We assume you already had a key pair generated using `ssh-keygen`.
$ ssh-copy-id -i ~/.ssh/id_rsa gitolite@gitserver $ ssh-copy-id -i ~/.ssh/id_rsa.pub gitolite@gitserver
This will ask you for the password to the gitolite account, and then set up public key access. This is **essential** for the install script, so check to make sure you can run a command without getting a password prompt: This will ask you for the password to the gitolite account, and then set up public key access. This is **essential** for the install script, so check to make sure you can run a command without getting a password prompt:

2
doc/ssh-troubleshooting.mkd
View file

@ -307,7 +307,7 @@ from scratch:
`sitaram`, along with corresponding `.pub` files). Create them if needed. `sitaram`, along with corresponding `.pub` files). Create them if needed.
Also make sure they are *different* and not a copy of each other :-) Also make sure they are *different* and not a copy of each other :-)
* install gitolite normally: * install gitolite normally:
* run `ssh-copy-id -i ~/.ssh/id_rsa git@server` to get passwordless * run `ssh-copy-id -i ~/.ssh/id_rsa.pub git@server` to get passwordless
access to the server. (Mac users may have to do this step manually) access to the server. (Mac users may have to do this step manually)
* make sure `ssh git@server pwd` prints the `$HOME` of `git@server` * make sure `ssh git@server pwd` prints the `$HOME` of `git@server`
**without** asking for a password. Do not proceed till this works. **without** asking for a password. Do not proceed till this works.