From f98b1971cb1b39c8fb4f13783817d325495567e5 Mon Sep 17 00:00:00 2001 From: Ben Anderson Date: Mon, 27 May 2019 15:54:31 +0000 Subject: Add documentation for using http_proxy with GitLab Pages. --- doc/administration/pages/index.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md index 9945bd02f26..3a7ca517d56 100644 --- a/doc/administration/pages/index.md +++ b/doc/administration/pages/index.md @@ -291,6 +291,20 @@ Pages access control is disabled by default. To enable it: 1. [Reconfigure GitLab][reconfigure]. 1. Users can now configure it in their [projects' settings](../../user/project/pages/introduction.md#gitlab-pages-access-control-core-only). +### Running behind a proxy + +Like the rest of GitLab, Pages can be used in those environments where external +internet connectivity is gated by a proxy. In order to use a proxy for GitLab +pages: + +1. Configure in `/etc/gitlab/gitlab.rb`: + + ```ruby + gitlab_pages['http_proxy'] = 'http://example:8080' + ``` + +1. [Reconfigure Gitlab][reconfigure] for the changes to take effect. + ## Activate verbose logging for daemon Verbose logging was [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2533) in -- cgit v1.2.1