From 4ed6e7ecdb8ac3c115299febdd5f6bbbbff716ee Mon Sep 17 00:00:00 2001 From: Sameer Naik Date: Thu, 16 Jul 2015 22:52:20 +0530 Subject: [PATCH] readme: cleanup ssl section --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c10e6ef3..08919889 100644 --- a/README.md +++ b/README.md @@ -442,14 +442,14 @@ docker run --name gitlab -d \ Access to the gitlab application can be secured using SSL so as to prevent unauthorized access to the data in your repositories. While a CA certified SSL certificate allows for verification of trust via the CA, a self signed certificates can also provide an equal level of trust verification as long as each client takes some additional steps to verify the identity of your website. I will provide instructions on achieving this towards the end of this section. +Jump to the [Using HTTPS with a load balancer](#using-https-with-a-load-balancer) section if you are using a load balancer such as hipache, haproxy or nginx. + To secure your application via SSL you basically need two things: - **Private key (.key)** - **SSL certificate (.crt)** When using CA certified certificates, these files are provided to you by the CA. When using self-signed certificates you need to generate these files yourself. Skip to [Strengthening the server security](#strengthening-the-server-security) section if you are armed with CA certified SSL certificates. -Jump to the [Using HTTPS with a load balancer](#using-https-with-a-load-balancer) section if you are using a load balancer such as hipache, haproxy or nginx. - #### Generation of Self Signed Certificates Generation of self-signed SSL certificates involves a simple 3 step procedure.