diff options
Diffstat (limited to 'doc/administration/pages/index.md')
| -rw-r--r-- | doc/administration/pages/index.md | 40 |
1 files changed, 20 insertions, 20 deletions
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md index c84e5eb8c8c..f64c53e28a2 100644 --- a/doc/administration/pages/index.md +++ b/doc/administration/pages/index.md @@ -141,8 +141,8 @@ The Pages daemon doesn't listen to the outside world. 1. Set the external URL for GitLab Pages in `/etc/gitlab/gitlab.rb`: ```ruby - external_url "http://gitlab.example.com" # external_url here is only for reference - pages_external_url "http://pages.example.com" # not a subdomain of external_url + external_url "http://example.com" # external_url here is only for reference + pages_external_url 'http://example.io' # Important: not a subdomain of external_url, so cannot be http://pages.example.com ``` 1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation). @@ -163,12 +163,12 @@ URL scheme: `https://<namespace>.example.io/<project_slug>` NGINX proxies all requests to the daemon. Pages daemon doesn't listen to the outside world. -1. Place the `example.io` certificate and key inside `/etc/gitlab/ssl`. +1. Place the wildcard LTS certificate for `*.example.io` and the key inside `/etc/gitlab/ssl`. 1. In `/etc/gitlab/gitlab.rb` specify the following configuration: ```ruby - external_url "https://gitlab.example.com" # external_url here is only for reference - pages_external_url "https://pages.example.com" # not a subdomain of external_url + external_url "https://example.com" # external_url here is only for reference + pages_external_url 'https://example.io' # Important: not a subdomain of external_url, so cannot be https://pages.example.com pages_nginx['redirect_http_to_https'] = true ``` @@ -211,8 +211,8 @@ This setup is primarily intended to be used when [installing a GitLab POC on Ama 1. In `/etc/gitlab/gitlab.rb` specify the following configuration: ```ruby - external_url "https://gitlab.example.com" # external_url here is only for reference - pages_external_url "https://pages.example.com" # not a subdomain of external_url + external_url "https://example.com" # external_url here is only for reference + pages_external_url 'https://example.io' # Important: not a subdomain of external_url, so cannot be https://pages.example.com pages_nginx['enable'] = true pages_nginx['listen_port'] = 80 @@ -334,8 +334,8 @@ world. Custom domains are supported, but no TLS. 1. In `/etc/gitlab/gitlab.rb` specify the following configuration: ```ruby - external_url "http://gitlab.example.com" # external_url here is only for reference - pages_external_url "http://pages.example.com" # not a subdomain of external_url + external_url "http://example.com" # external_url here is only for reference + pages_external_url 'http://example.io' # Important: not a subdomain of external_url, so cannot be http://pages.example.com nginx['listen_addresses'] = ['192.0.2.1'] # The primary IP of the GitLab instance pages_nginx['enable'] = false gitlab_pages['external_http'] = ['192.0.2.2:80', '[2001:db8::2]:80'] # The secondary IPs for the GitLab Pages daemon @@ -361,12 +361,12 @@ In that case, the Pages daemon is running, NGINX still proxies requests to the daemon but the daemon is also able to receive requests from the outside world. Custom domains and TLS are supported. -1. Place the `example.io` certificate and key inside `/etc/gitlab/ssl`. +1. Place the wildcard LTS certificate for `*.example.io` and the key inside `/etc/gitlab/ssl`. 1. In `/etc/gitlab/gitlab.rb` specify the following configuration: ```ruby - external_url "https://gitlab.example.com" # external_url here is only for reference - pages_external_url "https://pages.example.com" # not a subdomain of external_url + external_url "https://example.com" # external_url here is only for reference + pages_external_url 'https://example.io' # Important: not a subdomain of external_url, so cannot be https://pages.example.com nginx['listen_addresses'] = ['192.0.2.1'] # The primary IP of the GitLab instance pages_nginx['enable'] = false gitlab_pages['external_http'] = ['192.0.2.2:80', '[2001:db8::2]:80'] # The secondary IPs for the GitLab Pages daemon @@ -406,7 +406,7 @@ domain as a custom domain to their project. If your user base is private or otherwise trusted, you can disable the verification requirement: -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Settings > Preferences**. 1. Expand **Pages**. @@ -424,7 +424,7 @@ sites served under a custom domain. To enable it: 1. Choose an email address on which you want to receive notifications about expiring domains. -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Settings > Preferences**. 1. Expand **Pages**. @@ -478,7 +478,7 @@ pre-existing applications must modify the GitLab Pages OAuth application. Follow this: 1. Enable [access control](#access-control). -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Applications**. 1. Expand **GitLab Pages**. @@ -498,7 +498,7 @@ This can be helpful to restrict information published with Pages websites to the of your instance only. To do that: -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Settings > Preferences**. 1. Expand **Pages**. @@ -689,7 +689,7 @@ Prerequisite: To set the global maximum pages size for a project: -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Settings > Preferences**. 1. Expand **Pages**. @@ -704,7 +704,7 @@ Prerequisite: To set the maximum size of each GitLab Pages site in a group, overriding the inherited setting: -1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. On the left sidebar, select **Search or go to** and find your group. 1. On the left sidebar, select **Settings > General**. 1. Expand **Pages**. 1. Enter a value under **Maximum size** in MB. @@ -718,7 +718,7 @@ Prerequisite: To set the maximum size of GitLab Pages site in a project, overriding the inherited setting: -1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, select **Search or go to** and find your project. 1. On the left sidebar, select **Deploy > Pages**. 1. In **Maximum size of pages**, enter the size in MB. 1. Select **Save changes**. @@ -731,7 +731,7 @@ Prerequisite: To set the maximum number of GitLab Pages custom domains for a project: -1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. On the left sidebar, select **Search or go to**. 1. Select **Admin Area**. 1. On the left sidebar, select **Settings > Preferences**, and expand **Pages**. 1. Enter a value for **Maximum number of custom domains per project**. Use `0` for unlimited domains. |