Commit a6af8f0bb4404733e0d7396aa24a71723945408f
1 parent
4847f64c
Exists in
master
and in
13 other branches
Explain how to get to gitlab.yml via gitlab.rb
Showing
1 changed file
with
28 additions
and
0 deletions
Show diff stats
README.md
... | ... | @@ -184,6 +184,34 @@ sudo lokkit -p 2443:tcp |
184 | 184 | |
185 | 185 | Run `sudo gitlab-ctl reconfigure` for the change to take effect. |
186 | 186 | |
187 | +### Changing gitlab.yml settings | |
188 | + | |
189 | +This is an advanced topic. If you are already familiar with configuring GitLab | |
190 | +and you want to change a `gitlab.yml` setting, you need to do so via | |
191 | +`/etc/gitlab/gitlab.rb`. The translation works as follows. | |
192 | + | |
193 | +In `gitlab.yml`, you will find structure like this: | |
194 | + | |
195 | +```yaml | |
196 | +production: &base | |
197 | + gitlab: | |
198 | + default_projects_limit: 10 | |
199 | +``` | |
200 | + | |
201 | +In `gitlab.rb`, this translates to: | |
202 | + | |
203 | +```ruby | |
204 | +gitlab_rails['gitlab_default_projects_limit'] = 10 | |
205 | +``` | |
206 | + | |
207 | +What happens here is that we forget about `production: &base`, and join | |
208 | +`gitlab:` with `default_projects_limit:` into `gitlab_default_projects_limit`. | |
209 | +Note that not all `gitlab.yml` settings can be changed via `gitlab.rb` yet; if | |
210 | +you think an attribute is missing please create an issue on the omnibus-gitlab | |
211 | +issue tracker. | |
212 | + | |
213 | +Run `sudo gitlab-ctl reconfigure` for changes in `gitlab.rb` to take effect. | |
214 | + | |
187 | 215 | ## Backups |
188 | 216 | |
189 | 217 | ### Creating an application backup | ... | ... |