43 lines
1.6 KiB
Text
43 lines
1.6 KiB
Text
Template: gitlab/fqdn
|
||
Type: string
|
||
Default: localhost
|
||
_Description: Fully qualified domain name for this instance of Gitlab:
|
||
Please choose the domain name which should be used to access this
|
||
instance of Gitlab.
|
||
.
|
||
This should be the fully qualified name as seen from the Internet, with
|
||
the domain name that will be used to access the pod.
|
||
.
|
||
If a reverse proxy is used, give the hostname that the proxy server
|
||
responds to.
|
||
|
||
Template: gitlab/ssl
|
||
Type: boolean
|
||
Default: false
|
||
_Description: Enable https?
|
||
Enabling https means that an SSL certificate is required to access this Gitlab
|
||
instance (as Nginx will be configured to respond only to https requests). A
|
||
self-signed certificate is enough for local testing (and can be generated
|
||
using, for instance, the package easy-rsa), but it is not recommended for a
|
||
production instance.
|
||
.
|
||
Some certificate authorities like Let's Encrypt (letsencrypt.org), StartSSL
|
||
(startssl.com) or WoSign (buy.wosign.com/free) offer free SSL certificates.
|
||
.
|
||
letsencrypt package may be used to automate interaction with Let’s Encrypt to
|
||
obtain a certificate.
|
||
|
||
Template: gitlab/letsencrypt
|
||
Type: boolean
|
||
Default: false
|
||
_Description: Use Let's Encrypt?
|
||
Symbolic links to certificate and key created using letsencrypt package
|
||
(/etc/letencrypt/live) will be added to /etc/gitlab/ssl if this option is
|
||
selected.
|
||
.
|
||
Otherwise, certificate and key files have to be placed manually to
|
||
/etc/gitlab/ssl directory as 'gitlab.crt' and 'gitlab.key'.
|
||
.
|
||
Nginx must be reloaded after the certificate and key files are made available
|
||
at /etc/gitlab/ssl.
|