You can find the template for gitlab.rb at https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template. It is not updated after upgrades.
You can also use omnibus or GitLab to implement high availability (HA) for your GitLab installation.
There is a part in gitlab.rb where you can define the role of the GitLab instance you are configuring. If there are no roles defined by default, omnibus will configure your server to host all the core components of GitLab.
For instance, add the following line of code if your instance will run as a Redis master, and have the Redis sentinel agent running:
roles ['redis_sentinel_role', 'redis_master_role']
The following roles are available:
- redis_sentinel_role: Enables the sentinel service only.
- redis_master_role: Enables Redis and monitoring, and allows you to configure the master password.
- redis_slave_role: Enables the Redis service and monitoring.
- geo_primary_role: Configures the database for replication and prepares the application server as geo primary.
- geo_secondary_role: Prepares the database for replication and sets the application up as secondary geo.
- postgres_role: Switches on the postgresql, repmgr, and consul services on the machine. Sets up only these components.
- pgbouncer_role: This role adds the PgBouncer software for the database load-balancing feature.
After editing, you have to issue a gitlab-ctl reconfigure to apply the settings.