Commit f5716057c877bbded79fdeea5743219e8b8ec47f
Exists in
master
and in
2 other branches
Merge branch 'readme_env_settings' into 'master'
Readme env settings Add a section to the README detailing how to supply environment vars to Gitlab as implemented in https://gitlab.com/gitlab-org/omnibus-gitlab/commit/c76528182f3a9a3465ec0d2b560ac3d3d50858e1 See merge request !172
Showing
1 changed file
with
14 additions
and
0 deletions
Show diff stats
README.md
@@ -282,6 +282,20 @@ external_url "https://gitlab.example.com:2443" | @@ -282,6 +282,20 @@ external_url "https://gitlab.example.com:2443" | ||
282 | 282 | ||
283 | Run `sudo gitlab-ctl reconfigure` for the change to take effect. | 283 | Run `sudo gitlab-ctl reconfigure` for the change to take effect. |
284 | 284 | ||
285 | +### Adding ENV Vars to the Gitlab Runtime Environment | ||
286 | + | ||
287 | +If you need Gitlab to have access to certain environment variables, you can | ||
288 | +configure them in `/etc/gitlab/gitlab.rb`. This is useful in situations where | ||
289 | +you need to use a proxy to access the internet and you will be wanting to | ||
290 | +clone externally hosted repositories directly into gitlab. In `/etc/gitlab/gitlab.rb` | ||
291 | +supply a `gitlab_rails['env']` with a hash value. For example: | ||
292 | + | ||
293 | +```ruby | ||
294 | +gitlab_rails['env'] = {"http_proxy" => "my_proxy", "https_proxy" => "my_proxy"} | ||
295 | +``` | ||
296 | + | ||
297 | +Run `sudo gitlab-ctl reconfigure` for the change to take effect. | ||
298 | + | ||
285 | ### Changing gitlab.yml settings | 299 | ### Changing gitlab.yml settings |
286 | 300 | ||
287 | Some of GitLab's features can be customized through | 301 | Some of GitLab's features can be customized through |