GitLab Installation on Ubuntu Server 12.04

For the people not knowing what GIT is or what it’s used for here’s a link to read about it What is GIT. This post wouldn’t have been possible if it was not for the work done by the community at GitLab . Please donate to this project.


This installation was done on a Ubuntu 12.04 server. A clean install was done with no extra packages installed with the base installation. The server is setup on a VM running on VMWare ESX4.

The installation consists of 6 steps:

Install packages / dependencies
Install ruby
Install gitolite
Install and configure Gitlab.
Start the web front-end
Start a Resque worker (for background processing)

First 3 steps can be easily skipped with simply install script:

# Install curl and sudo
apt-get install curl sudo

# 3 steps in 1 command
curl | sh

Now you can go to step 4″

1. Install packages

Keep in mind that sudo is not installed for debian by default. You should install it with as root (to gain root access on Ubuntu login with your username and sudo -i ):

apt-get update && apt-get upgrade && apt-get install sudo

sudo apt-get update

sudo apt-get upgrade 

sudo apt-get install -y git-core wget curl gcc checkinstall libxml2-dev libxslt-dev sqlite3 libsqlite3-dev libcurl4-openssl-dev libreadline-dev libc6-dev libssl-dev libmysql++-dev make build-essential zlib1g-dev libicu-dev redis-server openssh-server git-core python-dev python-pip libyaml-dev sendmail 

# If you want to use MySQL: 
sudo apt-get install -y mysql-server mysql-client libmysqlclient-dev

2. Install Ruby

tar xzfv ruby-1.9.2-p290.tar.gz
cd ruby-1.9.2-p290
sudo make install

3. Install gitolite

Create user for git:

sudo adduser \
--system \
--shell /bin/sh \
--gecos 'git version control' \
--group \
--disabled-password \
--home /home/git \

Create user for gitlab:

# ubuntu/debian
sudo adduser --disabled-login --gecos 'gitlab system' gitlab

Add your user to git group:

sudo usermod -a -G git gitlab

Generate key:

sudo -H -u gitlab ssh-keygen -q -N '' -t rsa -f /home/gitlab/.ssh/id_rsa

Get gitolite source code:

cd /home/git
sudo -H -u git git clone git:// /home/git/gitolite


sudo -u git sh -c 'echo -e "PATH=\$PATH:/home/git/bin\nexport PATH" > /home/git/.profile'
sudo -u git -i -H /home/git/gitolite/src/gl-system-install
sudo cp /home/gitlab/.ssh/ /home/git/
sudo chmod 777 /home/git/
sudo -u git -H sed -i 's/0077/0007/g' /home/git/share/gitolite/conf/example.gitolite.rc
sudo -u git -H sh -c "PATH=/home/git/bin:$PATH; gl-setup -q /home/git/"


sudo chmod -R g+rwX /home/git/repositories/
sudo chown -R git:git /home/git/repositories/

CHECK: Logout & login again to apply git group to your user

# clone admin repo to add localhost to known_hosts
# & be sure your user has access to gitolite
sudo -u gitlab -H git clone git@localhost:gitolite-admin.git /tmp/gitolite-admin

# if succeed you can remove it
sudo rm -rf /tmp/gitolite-admin

IMPORTANT! If you cant clone gitolite-admin repository – DONT PROCEED INSTALLATION

4. Install gitlab and configuration. Check status configuration.

sudo gem install charlock_holmes
sudo pip install pygments
sudo gem install bundler
cd /home/gitlab
sudo -H -u gitlab git clone git:// gitlab
cd gitlab

# Rename config files
sudo -u gitlab cp config/gitlab.yml.example config/gitlab.yml

Select db you want to use

# SQLite
sudo -u gitlab cp config/database.yml.sqlite config/database.yml

# Or
# Mysql
sudo -u gitlab cp config/database.yml.example config/database.yml
# Change username/password of config/database.yml to real one

Install gems

sudo -u gitlab -H bundle install --without development test --deployment

Setup DB

sudo -u gitlab bundle exec rake gitlab:app:setup RAILS_ENV=production

Checking status:

sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production
Starting diagnostic
/home/git/repositories/ is writable?............YES
remote: Counting objects: 603, done.
remote: Compressing objects: 100% (466/466), done.
remote: Total 603 (delta 174), reused 0 (delta 0)
Receiving objects: 100% (603/603), 53.29 KiB, done.
Resolving deltas: 100% (174/174), done.
Can clone gitolite-admin?............YES
UMASK for .gitolite.rc is 0007? ............YES

If you got all YES – congrats! You can go to next step.

5. Server up

Application can be started with next command:

# For test purposes
sudo -u gitlab bundle exec rails s -e production

# As daemon
sudo -u gitlab bundle exec rails s -e production -d

6. Run resque process (for processing queue).

# Manually
sudo -u gitlab bundle exec rake environment resque:work QUEUE=* RAILS_ENV=production BACKGROUND=yes

# Gitlab start script

*Ok – we have a working application now. * *But keep going – there are some thing that should be done *

Nginx && Unicorn

Install Nginx

sudo apt-get install nginx


cd /home/gitlab/gitlab
sudo -u gitlab cp config/unicorn.rb.orig config/unicorn.rb
sudo -u gitlab bundle exec unicorn_rails -c config/unicorn.rb -E production -D

Edit /etc/nginx/nginx.conf. Add next code to http section:

upstream gitlab {
server unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket;

server {
listen YOUR_SERVER_IP:80;
root /home/gitlab/gitlab/public;

# individual nginx logs for this gitlab vhost
access_log /var/log/nginx/gitlab_access.log;
error_log /var/log/nginx/gitlab_error.log;

location / {
# serve static files from defined root folder;.
# @gitlab is a named location for the upstream fallback, see below
try_files $uri $uri/index.html $uri.html @gitlab;

# if a file, which is not found in the root folder is requested,
# then the proxy pass the request to the upsteam (gitlab unicorn)
location @gitlab {
proxy_redirect off;
# you need to change this to "https", if you set "ssl" directive to "on"
proxy_set_header X-FORWARDED_PROTO http;
proxy_set_header Host;
proxy_set_header X-Real-IP $remote_addr;

proxy_pass http://gitlab;

} – change to your domain.

Restart nginx:

/etc/init.d/nginx restart

Create init script in /etc/init.d/gitlab

#! /bin/bash
# Provides: gitlab
# Required-Start: $local_fs $remote_fs $network $syslog redis-server
# Required-Stop: $local_fs $remote_fs $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: GitLab git repository management
# Description: GitLab git repository management

DAEMON_OPTS="-c /home/gitlab/gitlab/config/unicorn.rb -E production -D"
DESC="Gitlab service"

case "$1" in
CD_TO_APP_DIR="cd /home/gitlab/gitlab"
START_DAEMON_PROCESS="bundle exec unicorn_rails $DAEMON_OPTS"

echo -n "Starting $DESC: "
if [ `whoami` = root ]; then
sudo -u gitlab sh -c "$CD_TO_APP_DIR > /dev/null 2>&1 && $START_DAEMON_PROCESS && $START_RESQUE_PROCESS"
echo "$NAME."
echo -n "Stopping $DESC: "
kill -QUIT `cat $PID`
kill -QUIT `cat $RESQUE_PID`
echo "$NAME."
echo -n "Restarting $DESC: "
kill -USR2 `cat $PID`
kill -USR2 `cat $RESQUE_PID`
echo "$NAME."
echo -n "Reloading $DESC configuration: "
kill -HUP `cat $PID`
kill -HUP `cat $RESQUE_PID`
echo "$NAME."
echo "Usage: $NAME {start|stop|restart|reload}" >&2
exit 1

exit 0

Adding permission:

sudo chmod +x /etc/init.d/gitlab

When server is rebooted then gitlab must starting:

sudo insserv gitlab

*This step didn’t work for me so what I did was to edit the rc.local file.

nano /etc/rc.local

And added the following to the rc.local file to start the GitLab when the server reboots

cd /home/gitlab/gitlab
sudo -u gitlab bundle exec unicorn_rails -c config/unicorn.rb -E production -D
/etc/init.d/nginx restart
sudo /etc/init.d/gitlab restart

Now you can


gitlab like:

sudo /etc/init.d/gitlab restart

Test your installation

If all went well, you should be able to connect to your server at http://yoursevername. The default login info is as follows:

password : 5ivel!fe

Enjoy your new GIT server!

Reference: GitLab


Test Comment