5 KiB
GitLab Pages Administration
Note: This feature was introduced in GitLab EE 8.3
If you are looking for ways to upload your static content in GitLab Pages, you probably want to read the user documentation.
Configuration
There are a couple of things to consider before enabling GitLab pages in your GitLab EE instance.
- You need to properly configure your DNS to point to the domain that pages will be served
- Pages use a separate Nginx configuration file which needs to be explicitly added in the server under which GitLab EE runs
Both of these settings are described in detail in the sections below.
DNS configuration
GitLab Pages expect to run on their own virtual host. In your DNS server/provider you need to add a wildcard DNS A record pointing to the host that GitLab runs. For example, an entry would look like this:
*.gitlab.io. 60 IN A 1.2.3.4
where gitlab.io
is the domain under which GitLab Pages will be served
and 1.2.3.4
is the IP address of your GitLab instance.
It is strongly advised to not use the GitLab domain to serve user pages. For more information see the security section.
Omnibus package installations
See the relevant documentation at http://doc.gitlab.com/omnibus/settings/pages.html.
Installations from source
-
Go to the GitLab installation directory:
cd /home/git/gitlab
-
Edit
gitlab.yml
and under thepages
setting, setenabled
totrue
and thehost
to the FQDN under which GitLab Pages will be served:## GitLab Pages pages: enabled: true # The location where pages are stored (default: shared/pages). # path: shared/pages # The domain under which the pages are served: # http://group.example.com/project # or project path can be a group page: group.example.com host: gitlab.io port: 80 # Set to 443 if you serve the pages with HTTPS https: false # Set to true if you serve the pages with HTTPS
-
Make sure you have copied the new
gitlab-pages
Nginx configuration file:sudo cp lib/support/nginx/gitlab-pages /etc/nginx/sites-available/gitlab-pages.conf sudo ln -sf /etc/nginx/sites-{available,enabled}/gitlab-pages.conf
Don't forget to add your domain name in the Nginx config. For example if your GitLab pages domain is
gitlab.io
, replaceserver_name ~^(?<group>.*)\.YOUR_GITLAB_PAGES\.DOMAIN$;
with
server_name ~^(?<group>.*)\.gitlabpages\.com$;
You must be extra careful to not remove the backslashes. If you are using a subdomain, make sure to escape all dots (
.
) with a backslash (). For examplepages.gitlab.io
would be:server_name ~^(?<group>.*)\.pages\.gitlab\.io$;
-
Restart Nginx and GitLab:
sudo service nginx restart sudo service gitlab restart
Running GitLab Pages with HTTPS
If you want the pages to be served under HTTPS, a wildcard SSL certificate is required.
-
In
gitlab.yml
, set the port to443
and https totrue
:## GitLab Pages pages: enabled: true # The location where pages are stored (default: shared/pages). # path: shared/pages # The domain under which the pages are served: # http://group.example.com/project # or project path can be a group page: group.example.com host: gitlab.io port: 443 # Set to 443 if you serve the pages with HTTPS https: true # Set to true if you serve the pages with HTTPS
-
Copy the
gitlab-pages-ssl
Nginx configuration file:sudo cp lib/support/nginx/gitlab-pages-ssl /etc/nginx/sites-available/gitlab-pages-ssl.conf sudo ln -sf /etc/nginx/sites-{available,enabled}/gitlab-pages.conf
Make sure to edit the config to add your domain as well as correctly point to the right location of the SSL certificate files. Restart Nginx for the changes to take effect.
Set maximum pages size
The maximum size of the unpacked archive per project can be configured in the Admin area under the Application settings in the Maximum size of pages (MB). The default is 100MB.
Change storage path
Pages are stored by default in /home/git/gitlab/shared/pages
.
If you wish to store them in another location you must set it up in
gitlab.yml
under the pages
section:
pages:
enabled: true
# The location where pages are stored (default: shared/pages).
path: /mnt/storage/pages
Restart GitLab for the changes to take effect:
sudo service gitlab restart
Backup
Pages are part of the regular backup so there is nothing to configure.
Security
You should strongly consider running GitLab pages under a different hostname than GitLab to prevent XSS attacks.