Installing gitolite
Intercepting git
- tags
- git
- gitolite
Contents
Setup
|
|
From your laptop, copy your public key
|
|
The back on the server:
|
|
Then checkout and install
|
|
Add a new server
OK, back on your laptop pull out the gitolite-admin
repo:
|
|
Then add a new repo inside of conf/gitolite.conf
|
|
And check it in to create the new repo
|
|
It's created the new repo. So, lets see if we can make it work. Clone repo, and then add a remote and push:
|
|
How does it work
When you first run setup, you pass it in a public key. This gets put
into .ssh/authorized_keys
, with the following options:
|
|
This means that everytime your user connects the server, it calls
gitolite-shell
with your user, that it can find via the ssh key.
If you try to connect directly, it will show you the repositories that you have access to
|
|
|
|
Create new repositories by checking out the gitolite-admin
repository,
changing the config file, and then an update hook will run gitolite
compile
and the new repository will be created.
On the server, you can look at the logs in ~/.gitolite/logs
which will
give you a sense of what it is doing.
|
|
The gitolite-shell
command is responsible for figuring out who you
are, what you are trying to do, and then it delgates things to the
native git commands, which will be one of git-upload-pack
,
git-receive-pack
, or git-upload-archive
.
References
Previously
Next