From cbc3ce905facc72bd0e7a787ff951b33ec81439e Mon Sep 17 00:00:00 2001
From: Ross McDonald <ross@stoplight.io>
Date: Mon, 21 May 2018 10:07:23 -0500
Subject: [PATCH] Add https settings

---
 articles/enterprise/components/gitlab.md | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/articles/enterprise/components/gitlab.md b/articles/enterprise/components/gitlab.md
index fe8577f..eea6e4c 100644
--- a/articles/enterprise/components/gitlab.md
+++ b/articles/enterprise/components/gitlab.md
@@ -29,7 +29,7 @@ Redis).
 >
 > GitLab must be able to receive incoming connections from the following components:
 >
-> * App
+> * API
 >
 > GitLab must be able to make outgoing connections to the following components:
 >
@@ -124,6 +124,24 @@ external_url 'http://stoplight.example.com:8080'
 > If you are configuring GitLab to send emails, set the `external_url` to the
 > URL of the **Stoplight App** component, and not GitLab itself.
 
+##### ssl
+
+To enable SSL, update the `external_url` setting with a `https://` prefix, which
+will enable SSL connections over port 443. Once updated, set the certificate and
+private key locations using the following configuration:
+
+```ruby
+nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.example.com.crt"
+nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/gitlab.example.com.key"
+```
+
+If you would like to _only_ serve requests over HTTPS, use the following
+configuration:
+
+```ruby
+nginx['redirect_http_to_https'] = true
+```
+
 ##### postgresql
 
 To configure GitLab to use an external database (ie, the database _not_ embedded