kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Reword pages daemon intro

Browse source
This commit is contained in:
Achilleas Pipinellis 2016-02-22 01:10:49 +02:00 committed by James Edwards-Jones
parent 2a484c6a29
commit 54c943a597
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/pages/administration.md
View file

@ -44,11 +44,12 @@ probably want to read the [user documentation](README.md).
## The GitLab Pages daemon ## The GitLab Pages daemon
Starting from GitLab EE 8.5, Pages make use of a separate tool ([gitlab-pages]), Starting from GitLab EE 8.5, Pages make use of a separate tool ([gitlab-pages]),
a simple HTTP server written in Go that serves GitLab Pages with CNAMEs and SNI a simple HTTP server written in Go that can listen on an external IP address
using HTTP/HTTP2. You are encouraged to read its [README][pages-readme] to fully and provide support for custom domains and custom certificates. The GitLab
understand how it works. Pages Daemon supports dynamic certificates through SNI and exposes pages using
HTTP2 by default.
What is supported when using the pages daemon: Here is a brief list with what it is supported when using the pages daemon:
- Multiple domains per-project - Multiple domains per-project
- One TLS certificate per-domain - One TLS certificate per-domain
@ -56,6 +57,9 @@ What is supported when using the pages daemon:
- Validation of certificate chain - Validation of certificate chain
- Validation of private key against certificate - Validation of private key against certificate
You are encouraged to read its [README][pages-readme] to fully understand how
it works.
--- ---
In the case of custom domains, the Pages daemon needs to listen on ports `80` In the case of custom domains, the Pages daemon needs to listen on ports `80`