{{Note| {{ic|git}} user must have its initial group set to {{ic|git}} (not {{ic|users}}). If the initial group is not {{ic|git}}, then all files created by the {{ic|git}} user will be owned by {{ic|git:users}} which will prevent GitLab from showing you a newly created repository (it will get stucked at the page where it tells you how to push to the new repository).}}

−

−

==gitlab-shell==

−

−

GitLab Shell is an ssh access and repository management software developed specially for GitLab.

−

−

Login as git:

−

−

# su - git

−

−

Clone gitlab shell:

−

−

$ git clone https://github.com/gitlabhq/gitlab-shell.git

−

$ cd gitlab-shell

−

−

Switch to the right version:

−

−

$ git checkout v1.4.0

−

−

Edit {{ic|config.yml}} and replace gitlab_url with something like {{ic|http://domain.com/}}:

Currently GitLab supports [[MySQL]] and [[PostgreSQL]]. [[MariaDB]] has not been officially tested but it works just fine.

Currently GitLab supports [[MySQL]] and [[PostgreSQL]]. [[MariaDB]] has not been officially tested but it works just fine.

−

===MariaDB===

+

=== MariaDB ===

[[pacman|Install]] {{Pkg|mariadb}} and {{Pkg|libmariadbclient}} from the [[official repositories]] and start the [[daemon]]. Create the database and do not forget to replace {{ic|your_password_here}} with a real one.

[[pacman|Install]] {{Pkg|mariadb}} and {{Pkg|libmariadbclient}} from the [[official repositories]] and start the [[daemon]]. Create the database and do not forget to replace {{ic|your_password_here}} with a real one.

Line 74:

Line 28:

$ mysql -u root -p

$ mysql -u root -p

−

mysql> CREATE DATABASE IF NOT EXISTS `gitlabhq_production` DEFAULT CHARACTER SET `utf8` COLLATE `utf8_unicode_ci`;

[[pacman|Install]] {{Pkg|postgresql}} and {{Pkg|libpqxx}} from the [[official repositories]]. Follow [[PostgreSQL#Installing_PostgreSQL]] to set it up and start the [[daemon]].

[[pacman|Install]] {{Pkg|postgresql}} and {{Pkg|libpqxx}} from the [[official repositories]]. Follow [[PostgreSQL#Installing_PostgreSQL]] to set it up and start the [[daemon]].

Line 98:

Line 52:

# sudo -u git -H psql -d gitlabhq_production

# sudo -u git -H psql -d gitlabhq_production

−

−

===MySQL===

−

−

If you are still in favor of {{AUR|mysql}}, follow the same commands as MariaDB.

−

−

==Gitlab==

−

−

===Installation===

−

−

Clone GitLab's repository:

−

# su - git

−

$ git clone https://github.com/gitlabhq/gitlabhq.git gitlab

−

$ cd gitlab

−

$ git checkout 5-2-stable

−

−

{{Note| You can change {{ic|5-2-stable}} to {{ic|master}} if you want the bleeding edge version, but do so with caution! Check github to see what is the latest stable version and replace above accordingly.}}

Note: Throughout the article, sudo is heavily used, assuming that the user that is running the commands is root or someone with equal privileges. There is no need to edit the sudoers file whatsoever. It is only used to change to the appropriate user. For more info read man sudo.

Installation

Note: In order to receive mail notifications, make sure to install a mail server. By default, Archlinux does not ship with one. The recommended mail server is postfix, but you can use others such as SSMTP, msmtp, sendmail, etc.

Basic configuration

First we need to rename the example file.

$ cp config/gitlab.yml.example config/gitlab.yml

The options are pretty straightforward. Open config/gitlab.yml with your favorite editor and edit where needed.
Make sure to change localhost to the fully-qualified domain name of your host serving GitLab where necessary.

Install gems

Tip: If you do not want to download any gem documentation, add gem: --no-rdoc --no-ri to /home/git/.gemrc. Be sure to add it as the git user in order to acquire the appropriate permissions.

Note: See bug #33327 for about system-wide gems. As a temporary solution the following packages will be installed as git user, make sure /home/git/.gemrc contains gem: ... --user-install. And then add the bin path to the PATH variable like so export PATH="$PATH:~/.gem/ruby/2.0.0/bin".

Note: When executing the below and you recieve `Could not verify the SSL certificate for https://rubygems.org/` see bug #GitHub-4095 most likely because you're behind a proxy that tries to inject a local certificate for SSL domains in order to verify its content

If you used MariaDB:

$ bundle install --deployment --without development test postgres

If you used PostgreSQL:

$ bundle install --deployment --without development test mysql

Note: Using --without group_name in bundle command line will ignore required packages for the mentioned groups.

Initialize Database

Note: Make sure the redis daemon is enabled and started, otherwise the following command will fail. To check the status and see if it's running execute systemctl status redis, if it's dead start it as per usual via systemctl start redis

Initialize database and activate advanced features:

$ bundle exec rake gitlab:setup RAILS_ENV=production

Note: If you recieve a error No such file or directory - /home/git/repositories/root then most likely you've changed the default configuration for GitLab and you'll need to modify all static paths in config/gitlab.yml and run the above command again to initialize the database!

Check status

With the following commands we check if the steps we followed so far are configured properly.

Edit /etc/nginx/sites-enabled/gitlab and change YOUR_SERVER_IP and YOUR_SERVER_FQDN to the IP address and fully-qualified domain name of the host serving Gitlab. As you can see nginx needs to access /home/gitlab/gitlab/tmp/sockets/gitlab.socket socket file. You have to be able to run sudo -u http ls /home/gitlab/gitlab/tmp/sockets/gitlab.socket successfully. Otherwise setup access to the directory:

# chgrp http /home/gitlab
# chmod u=rwx,g=rx,o= /home/gitlab

Restart gitlab.service, resque.service and nginx.

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. First we rename the example file and then we start unicorn:

Now edit config/unicorn.rb and add a listening port by uncommenting the following line:

listen "127.0.0.1:8080"

Tip: You can set a custom port if you want. Just remember to also include it in Apache's virtual host. See below.

Create a virtual host for Gitlab

Create a configuration file for Gitlab’s virtual host and insert the lines below adjusted accordingly. For the ssl section see LAMP#SSL. If you do not need it, remove it. Notice that the SSL virtual host needs a specific IP instead of generic. Also if you set a custom port for Unicorn, do not forget to set it at the BalanceMember line.

Running GitLab with rvm

Note: Version 1.9.3 is currently recommended to avoid some compatibility issues.

For the complete installation you will want to be the final user (e.g. git) so make sure to switch to this user and activate your rvm:

su - git
source "$HOME/.rvm/scripts/rvm"

Then continue with the installation instructions from above. However, the systemd scripts will not work this way, because the environment for the rvm is not activated. The recommendation here is to create to separate shell scripts for puma and sidekiq to activate the environment and then start the service: