Tools Index


1. Install Gitolite

Install Gitolite port first;

        $ prt-get depinst gitolite

2. Configure Gitolite

Create user and home directory;

        # useradd -r -s /bin/sh -U -m -d /srv/gitolite gitolite
        # usermod -p x gitolite

Permissions for /srv/gitolite/repositories directories should be 0750/drwxr-x---.

        # chown gitolite:gitolite /srv/gitolite
        $ chmod -R o-rx /srv/gitolite/repositories
        $ chmod -R g+rx /srv/gitolite/repositories
        $ chmod -R o+r /srv/gitolite/projects.list

Password is necessary so the user is not locked and can login via ssh. This password will not be used.

        # passwd gitolite

Copy public key that will be used for authenticating gitolite administrator, read ssh how to create one, key don't need to have password. If the server is on remote a remote machine you can use scp to copy the public key;

        $ scp /home/bob/.ssh/'s password:                              100%  390     0.4KB/s   00:00

Then on remote machine;

        # cp /home/admin/ /srv/
        # su - gitolite
        $ gitolite setup -pk
        Initialized empty Git repository in /srv/gitolite/repositories/gitolite-admin.git/
        Initialized empty Git repository in /srv/gitolite/repositories/testing.git/
        WARNING: /srv/gitolite/.ssh missing; creating a new one
        (this is normal on a brand new install)
        WARNING: /srv/gitolite/.ssh/authorized_keys missing; creating a new one
        (this is normal on a brand new install)
        $ rm
        $ exit
        $ ssh -v -i ~/.ssh/gitolite gitolite@localhost -p 2222

3. Gitolite Administration

Read how to setup ssh identities, gitolite documentation. Start by cloning gitolite-adimin;

        $ git clone git-admin:gitolite-admin

3.1. Recover Admin Account

First copy the key to remote server, in this example key is on same server;

        # install -o gitolite -g gitolite /home/bob/.ssh/ /srv/gitolite/

Update gitolite key with new key;

        # su - gitolite
        $ gitolite setup -pk
        $ rm
        $ exit

3.2. Users

Gitolite helps add and remove users from authorized_keys by allowing add or remove keys from keydir directory in clone.

3.2.1. Add User

        $ mv keydir/
        $ git add keydir
        $ git commit -m "Added bob public key"
        $ git push

3.2.2. Remove User

        $ git rm keydir/
        $ git commit -m "Removed bob public key"
        $ git push

3.3. Repositories

3.3.1. Add Repository

Add repository atom and user bob to devteam group, edit conf/gitolite.conf;

        @guests         =   gitweb
        @interns        =   bob alice
        @dev            =   fred mary joe
        @teamleads      =   mary
        @staff          =   @interns @dev @teamleads

        repo  @secret
            - = @guests
            option deny-rules = 1

        repo @floss
            RW+                     =   @dev @staff
            R                       =   @all

        repo @project
            RW+                     =   @teamleads
            -   master              =   @dev
            -   refs/tags/v[0-9]    =   @dev
            RW+ develop/            =   @dev
            RW+ feature/            =   @dev
            RW+ hot-fix/            =   @dev
            RW                      =   @dev
            R                       =   @interns

        repo gitolite-admin
            RW+     =   gitolite

        repo doc ports pmwiki assistant
            config gitweb.owner         =   "Team"
            config gitweb.category      =   "Projects"

        repo doc
            config gitweb.description   =   "Documentation"
            option     =  deploy-web-doc

        repo ports
            config gitweb.description   =   "System Ports"

        repo pmwiki
            config gitweb.description   =   "Wiki"
            option     =  deploy-web-doc

        repo assistant
            config gitweb.description   =   "Open Assistant"

        @secret    =   gitolite-admin
        @project   =   doc ports pmwiki assistant

Commit and push;

        $ git add -u
        $ git push

3.3.2 Rename Repository

Rename rep void to sysdoc, on remote host;

        # cd /srv/gitolite/repositories/
        # mv void.git doc.git

On workstation edit conf/gitolite.conf;

        repo doc
                RW+     =       bob

Commit and push;

        $ git add -u
        $ git push

3.3.3 Delete Repository

        # cd /srv/gitolite/repositories/
        # rm -rf doc.git

On workstation edit conf/gitolite.conf and remove doc.

4. Gitolite Hooks

This document creates three scripts, one is run when gitolite receives push to a project with hook active - deploy-web, second script is run under root user to allow operations where gitolite user have no rights, third one is project specific - File are support functions for deploy-web hook.

        cron --->
             (extracts/process tar)
                calls defined script
                to extract this case

               (ends in remote rep/hooks/post-receive.h00-deploy-web)
                creates package and
                set deploy script to

This example try to have a separate creation of a package and its deployment, in case deploy script is not on the same machine other method can be used to send the package.

A normal package will have a files.tar with all or new files to extract, if necessary a deleted file with the list of files to be removed and a project file with data about the package like new hash commit, or witch script to call to deploy.

Package is created under gitolite /srv/gitolite/deploy/ script and /srv/gitolite/deploy/, deploy in this example is called called by cron.

Note on OpenBSD all scripts must be changed to use other than bash, ksh.

4.1. Activate Hooks

Example from Cookbook how to apply hooks only to certain repos. Uncomment or add this line on /srv/gitolite/.gitolite.rc, within the %RC block;

        LOCAL_CODE => "$rc{GL_ADMIN_BASE}/local",

Uncomment the 'repo-specific-hooks' line in the rc file or add it to the ENABLE list if it doesn't exist.

        # allow repo-specific hooks to be added

Create directory on gitolite-admin clone;

        $ cd ~/gitolite-admin
        $ mkdir -p local/hooks/repo-specific

Now add your hooks to that directory, but instead of using the git "standard" names (pre-receive, post-receive, post-update), you use descriptive names (e.g. "deploy", "RSS-post", etc).

On remote run;

        # su - gitolite
        $ mkdir .gitolite/local/hooks/repo-specific
        $ gitolite setup

4.2. Deploy and Hook script

Create deploy directory on remote, /srv/gitolite/deploy was chosen to have less impact on the package system;

        $ sudo -u gitolite mkdir /srv/gitolite/deploy

Script /srv/gitolite/deploy/ receives call create_package "project-name" "git-dir" "valid oldrev/invalid" "newrev" "script/to/" from gitolite hook and creates a package.

        $ sudo -u gitolite cp conf/srv/gitolite/ /srv/gitolite/deploy/

Script /srv/gitolite/deploy/ loops for each package, extracts, order commit hashes to create final snapshot of files and call script to handle deploy.

        $ sudo -u gitolite cp conf/srv/gitolite/ /srv/gitolite/deploy/

4.3. Setup project hook

Project hooks create a package by calling script and deploy a package being called by Deploy script is a simple example that handle multiple web projects.

4.3.1. Hook Script

Create gitolite-admin/local/hooks/repo-specific/deploy-web.

Create /srv/gitolite/deploy/scripts/

Activate this hook, the idea is to start with this one as a template working and then implement the final one. Edit gitolite admin configuration file and activate:

        repo doc
            config gitweb.description   =   "Documentation"
            option     =  deploy-web-doc

Add, commit, and push the admin repo;

        $ git add local/hooks/repo-specific/hook-deployweb
        $ git add -u && git commit -m "added deploy hook"

Now we can test if our script is functioning by creating a branch on doc making a random change and push;

        $ cd doc
        $ git checkout -b deploy_branch

4.3.2. Deploy Script

Create /srv/gitolite/deploy/scripts/

Give permissions to access files;

        # mkdir /srv/deploy_dir
        # chown www:www /srv/deploy_dir

Add cron job to call deploy script every minute;

        # crontab -e
        # /etc/crontab: crond(8) configuration

        # this way it will log
        # * * * * * /srv/gitolite/deploy/
        # without log
        * * * * * /srv/gitolite/deploy/ > /dev/null 2>&1

        @hourly   ID=sys.hourly   /usr/sbin/runjobs /etc/cron/hourly
        @daily    ID=sys.daily    /usr/sbin/runjobs /etc/cron/daily
        @weekly   ID=sys.weekly   /usr/sbin/runjobs /etc/cron/weekly
        @monthly  ID=sys.monthly  /usr/sbin/runjobs /etc/cron/monthly

        # End of file

4.3.3. Debuging hooks

Comment gitolite admin repo script "if" and uncomment debug sections, this allow to source the file with environment of hook. Later you can delete this branch locally and remote and start fresh. To test if hook is called each time you push run;

        $ echo $(( ( RANDOM % 10 ) +1 )) >> index.html && git add -u && git commit -m "test deploy" && git push git

See if a file was created in /srv/gitolite/deploy with name of project and with environmental variables of gitolite script.

From now on you can test changes directly on /srv/gitolite/.gitolite/local/hooks/repo-specific/hook-deployweb and repeat above command to see the results or create a separate script with all variables generated by above script set so you don't have to push at all.

Change cron to debug check root email or call deploy script directly from command line after hook and deploy_web are working.

5. Gitweb

        $ prt-get depinst p5-cgi p5-cgi-session libcgi \
                        fcgiwrap spawn-fcgi highlight

5.1. Configure gitweb

Edit /etc/gitweb.conf

        our $git_temp = "/srv/www/gitweb_tmp";

        our $projects_list = "/srv/gitolite/projects.list";
        # The directories where your projects are. Must not end with a slash.
        our $projectroot = "/srv/gitolite/repositories";

        # Base URLs for links displayed in the web interface.
        our @git_base_url_list = qw(git://;

        our $projects_list_group_categories = 1;

5.2. Configure fcgiwrap

Edit /etc/rc.d/fcgiwrap to run as www user member of gitolite group;


5.3. Configure nginx

A link from gitweb don't work under grsecurity since user www can't follow simlink to root. Making a copy allows to later deploy via gitolite hook.


        # ln -s /usr/share/gitweb /srv/www


        # cp -r /usr/share/gitweb /srv/www

Add this to default or main nginx virtual server;

	location /git/gitweb.cgi {
            alias /srv/www/gitweb;
	    include fastcgi_params;
	    gzip off;
	    fastcgi_param   SCRIPT_FILENAME  /srv/www/gitweb/gitweb.cgi;
	    fastcgi_param   GITWEB_CONFIG    /etc/gitweb.conf;
	    fastcgi_pass    unix:/var/run/fcgiwrap.sock;

	location /git {
	    alias /srv/www/gitweb;
	    index gitweb.cgi;

5.4. Configure gitolite

Edit /srv/gitolite/.gitolite.rc, change UMASK and GIT_CONFIG_KEYS to;

        # default umask gives you perms of '0700'; see the rc file docs for
        # how/why you might change this
        UMASK                           =>  027,

        # look for "git-config" in the documentation
        GIT_CONFIG_KEYS                 =>  '.*',

Edit gitolite-admin/conf/gitolite.conf;

        repo doc
            config gitweb.owner         =   team
            config gitweb.description   =   Documentation
            config gitweb.category      =   Projects

        repo ports
            config gitweb.owner         =   team
            config gitweb.description   =   System ports
            config gitweb.category      =   Projects

6. Git-daemon

Configure to run as user;

Tools Index

This is part of the LeetIO System Documentation. Copyright (C) 2021 LeetIO Team. See the file Gnu Free Documentation License for copying conditions.