Updating GitLab to Version 5.2 on ArchLinux

Wed 22 May 2013 by Javex

I am using GitLab on my server and today I upgraded to version 5.2 mostly because a system update somehow broke my custom changes regarding certificate verification (it seems it is now included in gitlab-shell).

Anyway, I was faced with the issue that I couldn't push anymore and so I started an upgrade to get everything clean again. I am running in a local RVM so I have to do updates on all gems manually.

While doing all this I stumbled upon an issue that read like this:

unicorn is not part of the bundle. Add it to Gemfile.

To save you some time, there is an easy solution: GitLab seems to have switched from unicorn to puma and so you don't run unicorn anymore. Your new command is: RAILS_ENV=production bundle exec puma -C "/home/git/gitlab/config/puma.rb".

If you have systemd files you also need to make an update here, because contrary to unicorn which was of type simple, puma is forking. The new systemd file for it looks like this:

[Unit]

Description=Gitlab Puma Rails server
Requires=sidekiq

[Service]
Type=forking
SyslogIdentifier=gl-puma
User=git
PIDFile=/home/git/gitlab/tmp/pids/puma.pid
WorkingDirectory=/home/git/gitlab
TimeoutStartSec=600

ExecStart=/home/git/bin/gitlab.sh start
ExecReload=/bin/kill -HUP $MAINPID
ExecStop=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

My gitlab.sh only launches the RVM and then starts puma. Maybe I will go ahead and update the ArchLinux article for GitLab if I find the time and the original author agrees.


Comments