|
I have installed gitolite on a test account and here are the steps. Gitolite basically works by 'taking over' a spare SSH user. Because of this it does not need a 'custom app' because nothing is going to be routed over HTTP, only SSH. Since you do not have root access on our system you will be following the 'non-root' install procedure outlined in this tutorial. For step 1 you will add an additional SSH user to the account. This user will act as the host for the gitolite installation. In the tutorial this user is called 'gitolite'. For step 2 and 7 of the install you will be generating a series of SSH keys. Our documentation on how to do this is here. The command in step 3 would look like this,
Where webXXX is your server's real number and thekey.pub is the name of the key file you generated in step 2. You can also use any domain in place of webXXX.webfaction.com that is pointing to your server. The commands in step 4 are ran exactly as they are described in the tutorial. You will be logging in as the additional user created in step 1. If you are not sure how to connect with SSH to run the commands this documentation will outlined it. Step 5 is mostly the same rules as step 4, just remember to rename the key 'sena.pub' to whatever the name of the key file you created in step 2 and transferred to the server in step 3. Step 6 are commands you execute on your local PC. The command would look something like this,
Where 'gitolite' is your additional SSH username and 'webXXX.webfaction.com' has the real server number in place of XXX or is a domain pointing to the server. Step 7 is performed on your local PC as outlined. And that should be it. You do not need to install git as an application on your primary account, as the above installation sets up the git server in the home directory of the secondary user. |
