GitLab

The Gitlab overlay, originally the CVUT overlay, is currently on par with the latest GitLab version (13.8.0 as of January 2021). It supports GitLab migrations in a post-configure step, for those performing upgrades. The repo and issues can be found here.

Installation
The overlay may be added using either or.

To add using :

To add using :

GitLab requires the use of a database backend. Since version 12 PostgreSQL is the only supported database.

USE flags
The gitaly_git USE flag uses the bundled Git from gitlab-gitaly instead of dev-vcs/git. The puma USE flag is preselected because with GitLab 12.9 Puma has replaced Unicorn as the default web server. The systemd USE flag is preselected since the maintainer of the overlay ran out of OpenRC hosts for init script testing. :-) But with the help of some users of the overlay the OpenRC init scripts will be provided further on.

Preparations
Add the following keywords to be accepted by Portage (we use amd64 as architecture here; x86 is also available):

From GitLab 13.6 on Ruby 2.7 or later is required. Until Ruby 2.7 will be stabilized one must add further keywords to be accepted. As of January 2021 these were the following versions:

The overlay overrides the gentoo acct-user/git package introducing a new USE flag gitlab which creates the git user as required by www-apps/gitlabhq with HOME in /var/lib/gitlab/ and as member in the redis group. Add the USE Flag:

Emerge
Next emerge the package and follow the instructions given on the output (here the output of a 13.8.0 installation for an example).

Work through the list and finally run the configuration script (again with an example output).

You have to set the slots for gitlabhq and gitlab-gitaly otherwise GitLab won't work!

Files
TBD

OpenRC
Starting gitlabhq:

Current status:

Starting automatically at system boot:

systemd
Starting gitlabhq:

Current status:

Starting automatically at system boot:

Diagnostics
Run this command to get a full diagnostic.

Usage
TBD

Upgrade
TBD

External Resources
TBD