This project is a fork of the girocco.git project. If you have that one already cloned locally, you can use
git clone --reference /path/to/your/girocco.git/incarnation mirror_URL
to save bandwidth during cloning.
descriptionGirocco README
repository URLgit://
last changeThu, 11 Oct 2018 03:18:12 +0000 (11 05:18 +0200)
last refreshSat, 20 Oct 2018 10:22:20 +0000 (20 12:22 +0200)
content tags


Petr Baudis <>

This is the duct tape that ties together, codenamed Girocco. It is packaged here for easy re-deployment - just follow the INSTALL file for brief deployment instructions; you may hit some obstacle here or there, though, so be prepared.

Girocco is an Open Source project covered by the GNU General Public License. See the file COPYING for further details.

About Girocco

Girocco is a Git hosting solution, designed to allow users easily create and access repositories over the web, either in mirror mode (Girocco maintains a clone of the given repository locally) or in push mode (Girocco maintains a secure chroot with ssh inside for push-only access). A well-known feature is forking support, where users can easily publish modifications of projects they don't own, and mob user support, allowing a sandbox within a project where anonymous pushing is allowed.

Typical scenarios are:

Girocco itself comprises of a terse documentation, somewhat customized gitweb instance, CGI scripts for user and project management, and several management scripts for the hosting site maintenance.

Girocco vs...

Requirements and setup

You will need git pre-installed, or you can build and install one from the git.git subdirectory; normally, Girocco will use only gitweb from there. However, some bits of Girocco (e.g. the chroot setup) will rely on /usr/bin/git regardless of cmd_git settings; for chroot you will also need /bin/nc.openbsd (netcat-openbsd debian package). You will need to add the right users to the right groups (a dedicated Girocco user and the CGI user, at least); root access or root user cooperation will be probably essential unless you have good suexec setup. Girocco is designed to be run only with single instance within one system. If you want git protocol access, you will need to set up git-daemon independently, but it's very easy with inetd.

After configuring Girocco (editing Girocco/ and possibly other files), you should try to run make install and carefully look at any errors. See INSTALL for details. The installation procedure (especially chroot setup) is tuned for Debian systems, elsewhere you might need to adjust few things.

You should be running at all times - it will periodically check all the repositories and check if any need garbage collection, but also update them if the mirroring mode is enabled.

If you enable mirror support or want to have push notifications, you must also be running - it will listen to clone requests and perform the actual clone operations, and listen to notification messages from repository post-receive hooks and perform notifications.

If you enable push support, you will have to run sshd as root from within the chroot setup by make install; no special setup of the sshd is necessary, up to specifying a port to listen at in etc/ssh/sshd_config within the chroot (if the port is not to be 22).

Alternately, you can use push support with extremely relaxed security, but using the system-wide password database and not requiring a chroot. Or you could implement Gitosis permission model and send me a patch. ;-)

History and naming

Until Jul 2008, we called all the machinery just 'repo', however that is not very good name, especially since the machinery is now suitable for universal usage even outside of Thankfully, Jan Engelhart invented a nice name 'Girocco', standing for 'GIt Repo.Or.Cz COdebase'.

At that time, the machinery was a set of ugly cronjobs completely specific for However, Novartis sponsored an internship for Pasky to generalize the framework and adapt it for an internally suitable usage. And another year later, Pasky finally finished the job by porting Girocco back to useable state for and further cleaning it up.


An important Girocco concept is a project fork - anyone can fork any project (including a fork of another project), the fork resides in the directory structure as PARENT/FORK.git. Forks are meant as a place for people to freely publish their modifications for the project, even if they don't have push permissions to the parent. To save space and bandwidth, the fork will reuse objects in the parent project, garbage collection is done in a clever way not to prune objects used in forks.

Implementation of project database

(All uids and gids are allocated from range 65536..infty. All passwords are stored in DES crypt(3) format because Apache is moronic - in the past the group file was also used as htpasswd file.)

When you register a project, it will get a gid allocation and you will set a password for it. The triple is stored in a group(5) file (but containing just the project groups):


When you register a user, it will get a uid allocation and you will upload an ssh public key for it. The user is stored in a passwd(5) file (but containing just the users; 65534 is nogroup):


The authorized keys are stored in /etc/sshkeys/username.

When you (un)assign user to a project, you just manipulate the list of users for the project in /etc/group. The web interface for the project administration is protected by the group password.

If the given project is in push mode, that is indicated by having a .nofetch file in the repository. If the given project is in mirror mode on the other hand, that is indicated by the absence of .nofetch and by having double colon after the gid in the group(5) file - this prevents listed users to actually have write access to the repository.

9 days ago The repo.or... acme: sed off more pedanticallyrorcz
9 days ago The repo.or... acme: update certs location and computed chain
9 days ago The repo.or... switch all URLs from http: to https:
2018-10-06 The repo.or... indextext.html: remove reference to unavailable page
2018-10-06 Kyle J. McKayMerge branch 'master' into rorcz
2018-10-06 Kyle J. McKaydocs: make custom root info removablemaster
2018-10-01 Daniel Knittl... Update landing page info text
2018-10-01 Daniel Knittl... Fix working directory path in issue helper script
2018-10-01 Daniel Knittl... Make acme scripts executable
2018-10-01 Daniel Knittl... Enable letsencrypt in apache config
2018-10-01 Daniel Knittl... Add scripts
2018-08-26 Daniel Knittl... Add note about migration to Let's Encrypt certs
2018-08-21 Kyle J. McKayMerge branch 'master' into rorcz
2018-03-22 Kyle J. add repack dir links to logs and worktrees
2018-03-21 Kyle J. McKayMerge branch 'master' into rorcz
2018-03-15 Kyle J. --no-full mode can generate...
8 years ago girocco-1.0
9 days ago rorcz
2 weeks ago master
7 years ago wip/ugly-hack
7 years ago wip/recaptcha
8 years ago mob
8 years ago oldrepo