2016-01-16 15:43:30 +05:30
|
|
|
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.
|
2015-10-24 13:00:34 +05:30
|
|
|
|
|
|
|
|
Template: gitlab/ssl
|
|
|
|
|
Type: boolean
|
|
|
|
|
Default: true
|
|
|
|
|
_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
|
|
|
|
|
recommended for a production instance.
|
|
|
|
|
.
|
|
|
|
|
Some certificate authorities like StartSSL (startssl.com) or WoSign
|
|
|
|
|
(buy.wosign.com/free) offer free SSL certificates.
|
|
|
|
|
.
|
|
|
|
|
You can disable https if you want to access Gitlab only locally, via
|
|
|
|
|
Unicorn on port 3000. If you disable https, Nginx configuration will be
|
|
|
|
|
skipped.
|
