Setting up a Gitlab server

tested on debian/buster

Requirements

quite some power (at least 4 cores) and RAM are required (say 4 to 8 G)

make sure you’ve got outbound email alright and also static name resolution so gitlab@ points to itself and triggers the alias

vi /etc/aliases

gitlab: SOME-REAL-ADDRESS

newaliases
grep FQDN /etc/hosts

Install

curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | bash
apt install gitlab-ee
ls -lF /opt/gitlab/

#gitlab-ctl reconfigure

New root password

gitlab-rails console -e production

user = User.find_by_username 'root'
user.password = 'SOME-PASSWORD'
user.password_confirmation = 'SOME-PASSWORD'
user.send_only_admin_changed_your_password_notification!
user.save!
^D

rm /etc/gitlab/initial_root_password
ls -lF /opt/gitlab/etc/gitlab-rails-rc

Setup w/ SSL

make some certificates available e.g. into

/etc/gitlab/certs/

and proceed

mv -i /etc/gitlab/gitlab.rb /etc/gitlab/gitlab.rb.dist
vi /etc/gitlab/gitlab.rb

external_url 'https://gitlab.domain.tld'

nginx['enable'] = true
nginx['redirect_http_to_https'] = true
nginx['ssl_certificate'] = "/etc/gitlab/certs/ECC/_domain.tld/fullchain.pem"
nginx['ssl_certificate_key'] = "/etc/gitlab/certs/ECC/_domain.tld/privkey.pem"

moar options

#     allow_username_or_email_login: false
#     block_auto_created_users: false
#     lowercase_usernames: false
#     smartcard_auth: false

Ready to go

gitlab-ctl reconfigure
gitlab-rake gitlab:env:info

netstat -lntup | grep -v 127.0.0.1: | grep -v ::1:

eventually setup pass-through haproxy

https://gitlab.domain.tld/admin

admin area / settings / general
sign-up restrictions
    X sign-up enabled
    email confirmation: soft
    user cap: 100
    (save changes)