Hosting git Git Repositories - Git Recipes - page 467

The command $ ssh git@localhost will succeed only when issued by ad-
ministrator. If any other user tries to use ssh to git@localhost he or she will only
see the information about his or her current privileges:

hello peter, this is gitolite 2.2-1 (Debian) running on
git 1.7.9.5
the gitolite config gives you the following access:
R

W 06-07

@R_ @W_ testing

Summary

The recipes in this chapter concern mainly the tasks that are usually performed by
someone with root access to your host. To avoid the risk of messing with the host your
organization uses for its every day work, I decided to explain administrative tasks using
the virtual machine. Working that way you can drill and practice how to install and re-
move packages in your system without the slightest risk.
I prepared these recipes for beginners without previous experience with vagrant or
ssh. The only assumption I made was that you would be familiar with all the recipes
from previous chapter. Therefore, I included all the necessary background. Moreover,
every recipe is complete. This may make the recipes a little longer to run, but I believe
they will be easier to follow.
Depending on your needs, in my opinion, the following are the best choices you can
make:

• If you want to host private repositories with the ability to define access
rules—follow Recipe 11-10.

• If you want to host private repositories without the ability to define access
rules (every user has full access to all repositories)—follow Recipe 11-5.

• If you want to host publicly available repositories—follow Recipe 11-6.
• If you need web interface for your repositories use cgit—follow Recipe
11-9.

The protocols used by git