Permalink
Browse files

make the phrase "hosting user" a link in most places

  • Loading branch information...
1 parent 3b870cc commit 393cfcaa4c12decc19275356a34656f909a1202c @sitaramc committed Dec 9, 2012
Showing with 9 additions and 8 deletions.
  1. +1 −1 WARNINGS.mkd
  2. +1 −1 emergencies.mkd
  3. +1 −1 gsmigr.mkd
  4. +1 −1 install.mkd
  5. +2 −2 qi.mkd
  6. +1 −1 rare.mkd
  7. +2 −1 setup.mkd
View
@@ -3,7 +3,7 @@
Gitolite does NOT like it if you fiddle with files, directories, permissions,
etc., on the server except as directed in the documentation. Gitolite also
expects all the directories and files it manages/uses to be owned by the
-hosting user and not have strange permissions and ownerships.
+[hosting user][nnc] and not have strange permissions and ownerships.
Very few people have fallen foul of this, but the ones who *did* became very
obnoxious about it, hence this warning.
View
@@ -139,7 +139,7 @@ the answer, but here's a list of files you should blow away.
## #nonstd non-standard configs that'll trip you up
* having sshd setup to put the authorized\_keys file somewhere other than
- the default (which is in .ssh in the hosting user's home directory).
+ the default (which is in .ssh in the [hosting user][nnc]'s home directory).
* having sshd setup to not allow incoming ssh for the hosting user. Check
things like 'Allowusers' setting in /etc/ssh/sshd\_config etc.
View
@@ -30,7 +30,7 @@ Here are the steps on the server:
uses the update hook for checking write access.
* (as 'root' on the server) copy all of `~/repositories` to the gitolite
- hosting user's home directory. Something like
+ [hosting user][nnc]'s home directory. Something like
cp -a /home/gitosis/repositories /home/git
chown -R git.git /home/git/repositories
View
@@ -15,7 +15,7 @@ TOC
----
-## notes and naming conventions
+## #nnc notes and naming conventions
Gitolite uses a single "real" (i.e., unix) user to provide secure access to
git repos to any number of "virtual" users, without giving them a shell.
View
4 qi.mkd
@@ -12,15 +12,15 @@
* "your-name.pub" is your public key from your workstation.
* Also, this key does not already have shell access to this gitolite
- hosting user.
+ [hosting user][nnc].
* The setup command does not generate any warnings.
* If it does, please see [common errors][ce] and fix things before
continuing, or read the more complete [setup][] page.
## instructions
-On the server, as the hosting user (e.g., 'git'):
+On the server, as the [hosting user][nnc] (e.g., 'git'):
# get the software
git clone git://github.com/sitaramc/gitolite
View
@@ -11,7 +11,7 @@ On the server:
* They are all *bare* repos.
* All the repo names end in ".git".
* All the files and directories are owned and writable by the gitolite
- hosting user (especially true if you copied them as root).
+ [hosting user][nnc] (especially true if you copied them as root).
* Run `gitolite setup`. **If you forget this step, you can also forget
about write access control!**
View
@@ -10,7 +10,8 @@ always the "setup" command.
The first time you run it, you need to have a public key file (usually from
the admin's workstation) ready. If the main gitolite admin's username is
-"alice", this file should be named "alice.pub". Then run
+"alice", this file should be named "alice.pub". Then, as the [hosting
+user][nnc], run:
gitolite setup -pk alice.pub

0 comments on commit 393cfca

Please sign in to comment.