mount: wrong fs type, bad option, bad superblock on.Only the primary GitLab application server should Run touch /etc/gitlab/skip-auto-migrations to prevent database migrationsįrom running on upgrade. Secondary servers prior to running the first reconfigure in the steps GitLab server in /etc/gitlab/gitlab-secrets.json. These values can be obtained from the primary Extra configuration for additional GitLab application serversĪdditional GitLab servers (servers configured after the first GitLab server)Ĭonfigure shared secrets. IfĬertificates are not present, Nginx will fail to start. Note: When you specify https in the external_url, as in the exampleĪbove, GitLab assumes you have SSL certificates in /etc/gitlab/ssl/. WARNING: Only run this setup task on NEW GitLab instances because it Initialize the database by running sudo gitlab-rake gitlab:setup.It is not necessary to run this on additional application servers. Run sudo gitlab-ctl reconfigure to compile the configuration.Īs a final step, run the setup rake task on the first GitLab application server. Route traffic to all GitLab application servers in the HA cluster. In a typical HA setup, this will be the url of the load balancer which will Servers should point to the external url that users will use to access GitLab. On the first application server as well as the additional application Note: To maintain uniformity of links across HA clusters, the external_url external_url '' # Prevent GitLab from starting if NFS data mounts are not available high_availability = '/var/opt/gitlab/git-data' # Disable components that will not be on the GitLab application server roles # PostgreSQL connection details gitlab_rails = 'postgresql' gitlab_rails = 'unicode' gitlab_rails = '10.1.0.5' # IP/hostname of database server gitlab_rails = 'DB password' # Redis connection details gitlab_rails = '6379' gitlab_rails = '10.1.0.6' # IP/hostname of Redis server gitlab_rails = 'Redis Password' The example below assumes you'veĪdded NFS mounts in the default data locations. See NFS documentation for /etc/gitlab/gitlab.rbĬonfiguration values for various scenarios. Depending your the NFS configuration, you may need to change some GitLabĭata locations. mkdir -p /var/opt/gitlab/.ssh /var/opt/gitlab/gitlab-rails/uploads /var/opt/gitlab/gitlab-rails/shared /var/opt/gitlab/gitlab-ci/builds /var/opt/gitlab/git-dataĭownload/install GitLab Omnibus using steps 1 and 2 fromĬreate/edit /etc/gitlab/gitlab.rb and use the following configuration.īe sure to change the external_url to match your eventual GitLab front-end These may be different depending on your NFS Here is an example snippet to add to /etc/fstab: 10.1.0.1:/var/opt/gitlab/.ssh /var/opt/gitlab/.ssh nfs defaults,soft,rsize=1048576,wsize=1048576,noatime,nofail,lookupcache=positive 0 2 10.1.0.1:/var/opt/gitlab/gitlab-rails/uploads /var/opt/gitlab/gitlab-rails/uploads nfs defaults,soft,rsize=1048576,wsize=1048576,noatime,nofail,lookupcache=positive 0 2 10.1.0.1:/var/opt/gitlab/gitlab-rails/shared /var/opt/gitlab/gitlab-rails/shared nfs defaults,soft,rsize=1048576,wsize=1048576,noatime,nofail,lookupcache=positive 0 2 10.1.0.1:/var/opt/gitlab/gitlab-ci/builds /var/opt/gitlab/gitlab-ci/builds nfs defaults,soft,rsize=1048576,wsize=1048576,noatime,nofail,lookupcache=positive 0 2 10.1.0.1:/var/opt/gitlab/git-data /var/opt/gitlab/git-data nfs defaults,soft,rsize=1048576,wsize=1048576,noatime,nofail,lookupcache=positive 0 2Ĭreate the shared directories. The exact contents of /etc/fstab will depend on how you chose If necessary, install the NFS client utility packages using the followingĬommands: # Ubuntu/Debian apt-get install nfs-common # CentOS/Red Hat yum install nfs-utils nfs-utils-lib These additional steps before proceeding with GitLab installation. Note: There is some additional configuration near the bottom forĪdditional GitLab application servers. Complete the steps belowįor each GitLab application server in your environment. Assuming you have already configured a database, Redis, and NFS, you canĬonfigure the GitLab application server(s) now.