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

cbreak on #git: "I did bet that there are hundreds of sitaram admins out there"

Browse source 
Well from now on they will be called "YourName".

Even better quote from essial on #git (after literally typing in
"sitaram.pub" instead of substituting his name as the instructions [in
bold] tell him to do):

    come on you know how ubuntu users are
    if they see fixed width fonts inside a box they immediately copy-paste it

UBUNTU USERS: I DIDN'T SAY THAT, SOMEONE ELSE DID!  For details see
http://colabti.org/irclogger/irclogger_log/git?date=2010-11-04#l2417

[Although, since you apparently are quite happy to use a system that
default installs mono I doubt these little jibes matter to you
anyway...]

[idea: distribute my own pubkey with gitolite and instantly get access
to every gitolite install that is not behind a firewall, anywhere in the
world.  No one will notice or realise what I'm doing - MUAHAHAHAHA!!!]
This commit is contained in:
Sitaram Chamarty 2010-11-05 06:36:35 +05:30
parent 7ddc3ea4c6
commit 9716e32456
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/1-INSTALL.mkd
View file

@ -74,7 +74,7 @@ don't know ssh it'll be a nightmare to support you.
#### conventions used
Throughout the documentation, we use "sitaram" as the admin user, and his
Throughout the documentation, we use "YourName" as the admin user, and his
workstation is called "client". The hosting user is "git", and the server is
called "server". **Please substitute your values as needed**.
@ -156,12 +156,12 @@ easy -- the steps required for upgrading are marked "(U)".
#### (package method) directly on the server, using RPM/DEB
* from your workstation, copy your `~/.ssh/id_rsa.pub` file to the server.
Put it in `/tmp/sitaram.pub`.
Put it in `/tmp/YourName.pub`.
* (U) on the server, as root, do the install (urpmi, yum, apt-get, etc.).
* on the server, "su - git", then as "git" user, run `gl-setup
/tmp/sitaram.pub`.
/tmp/YourName.pub`.
* on the client, run `cd; git clone git@server:gitolite-admin`
@ -170,7 +170,7 @@ easy -- the steps required for upgrading are marked "(U)".
#### (root method) directly on the server, manually, with root access
* from your workstation, copy your `~/.ssh/id_rsa.pub` file to the server.
Put it in `/tmp/sitaram.pub`.
Put it in `/tmp/YourName.pub`.
* (U) on the server, as root, do the following:
@ -183,7 +183,7 @@ easy -- the steps required for upgrading are marked "(U)".
src/gl-system-install /usr/local/bin /usr/local/share/gitolite/conf /usr/local/share/gitolite/hooks
* on the server, "su - git", then as "git" user, run `gl-setup
/tmp/sitaram.pub`.
/tmp/YourName.pub`.
* on the client, run `cd; git clone git@server:gitolite-admin`
@ -197,7 +197,7 @@ 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.
* from your workstation, copy your `~/.ssh/id_rsa.pub` file to the server.
Put it in `/tmp/sitaram.pub`.
Put it in `/tmp/YourName.pub`.
* if `$HOME/bin` is not on the default PATH, fiddle with your `.bashrc` or
`.bash_profile` or similar files and add it somehow.
@ -212,7 +212,7 @@ server so that if you screw up the keys you can still get on, or be able to
mkdir -p $HOME/bin $HOME/share/gitolite/conf $HOME/share/gitolite/hooks
src/gl-system-install $HOME/bin $HOME/share/gitolite/conf $HOME/share/gitolite/hooks
* on the server, still as "git", run `gl-setup /tmp/sitaram.pub`.
* on the server, still as "git", run `gl-setup /tmp/YourName.pub`.
* on the client, run `cd; git clone git@server:gitolite-admin`