-
Amy Qualls authored
These pages had no metadata at all. Add it in, so the pages are counted.
Amy Qualls authoredThese pages had no metadata at all. Add it in, so the pages are counted.
stage: Systems
group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab.yml
and application.yml
settings (FREE SELF)
Changing Some GitLab features can be customized through
gitlab.yml
. If you want to change a gitlab.yml
setting
with Omnibus GitLab, you need to do so via /etc/gitlab/gitlab.rb
. The
translation works as follows. For a complete list of available options, visit the
gitlab.rb.template
.
New installations starting from GitLab 7.6, will have
all the options of the template listed in /etc/gitlab/gitlab.rb
by default.
In gitlab.yml
, you will find structure like this:
production: &base
gitlab:
default_theme: 2
In gitlab.rb
, this translates to:
gitlab_rails['gitlab_default_theme'] = 2
What happens here is that we forget about production: &base
, and join
gitlab:
with default_theme:
into gitlab_default_theme
.
Note that not all gitlab.yml
settings can be changed via gitlab.rb
yet; see
the gitlab.yml.erb
template.
If you think an attribute is missing please create a merge request on the Omnibus GitLab repository.
Run sudo gitlab-ctl reconfigure
for changes in gitlab.rb
to take effect.
Do not edit the generated file in /var/opt/gitlab/gitlab-rails/etc/gitlab.yml
since it will be overwritten on the next gitlab-ctl reconfigure
run.
gitlab.yml
Adding a new setting to Don't forget to update the following 5 files when adding a new setting:
- the
gitlab.rb.template
file to expose the setting to the end user via/etc/gitlab/gitlab.rb
. - the
default.rb
file to provide a sane default for the new setting. - the
gitlab.yml.example
file to actually use the setting's value fromgitlab.rb
. - the
gitlab.yml.erb
file - the
gitlab-rails_spec.rb
file