This is an old revision of the document!
- gitlab-ce
- Jonathan Haack
- Haack's Networking
- netcmnd@jonathanhaack.com
Installing gitlab-ce on a Debian system.
The pre-requisites:
- Self Hosted Web Server using Apache 2.4
- Available Domain with DNS set up
- Self-Signed Certificate is established as backup
- Letsencrypt, using certbot, is established and working
If you are missing some of these pre-requisites, please visit the Apache Survival Tutorial I created which covers these topics.
sudo apt install gitlab-ce sudo nano /etc/gitlab/gitlab.rb
In this file, you need to edit 6 lines. The Gitlab Tutorial requests an additional line - which I included but commented out - be adjusted and also forgets to specify that gitlab_workhorse should be enabled.
external_url 'http://gitlab.example.fr' gitlab_workhorse['enable'] = true gitlab_workhorse['listen_network'] = "tcp" gitlab_workhorse['listen_addr'] = "127.0.0.1:8181" web_server['external_users'] = ['www-data'] nginx['enable'] = false #gitlab_rails['trusted_proxies'] = [ '192.168.1.0/24', '192.168.2.1', '2001:0db8::/32' ]
Ok, now that the configuration file is set up, let's make sure that your Apache Web Server has appropriate configuration files. There is a Gitlab Recipes repository dedicated to getting Gitlab-CE up on non-default web servers. These templates were created by sysadmins from the Red Hat / Fedora family as can be seen by the directories for the log files, the service restarting commands, etc. I tweaked both omnibus24 configs for Debian as follows:
- Unordered List Item
— oemb1905 2018/08/04 11:52
