|
 |
4ce244f |
Care was taken to make the gitolite deployment from RPM as close to the
|
|
|
4ce244f |
upstream's way of installing gitolite. Therefore, the documentation shipped
|
|
|
4ce244f |
with the package should be useful and gl-install a gl-easy-install scripts
|
|
|
4ce244f |
should work.
|
|
|
4ce244f |
|
|
|
4ce244f |
The "easy" installation should be done as follows:
|
|
|
4ce244f |
|
|
 |
716ea29 |
1.) Add your key to ~gitolite/.ssh/authorized_keys
|
|
|
716ea29 |
2a.) If gitolite is running on the same machine, that you are using, run:
|
|
|
716ea29 |
gl-easy-install gitolite localhost $LOGNAME
|
|
|
716ea29 |
2b.) If gitolite is running on another machine, run on your local machine:
|
|
|
716ea29 |
gl-easy-install gitolite <hostname> <your_gitolite_username>
|
|
|
4ce244f |
3.) gitolite-admin is cloned. Now you can add repositories by modyfing
|
|
|
4ce244f |
configuration there and pushing it back.
|
|
|
4ce244f |
|
|
|
4ce244f |
The other way to do that would be to su to gitolite user, run "gl-install",
|
|
|
4ce244f |
follow the instructions and then manually populate the gitolite-admin.git
|
|
|
4ce244f |
repository (and recompile the configuration, as you'd be instructed).
|
|
|
4ce244f |
|
|
|
4ce244f |
To access the repositories, always use "gitolite" as user name. Gitolite
|
|
|
4ce244f |
doesn't use UNIX users/permissions to implement access control, it implements
|
|
|
4ce244f |
its own and determines the user name from the key used.
|