From 92f29f2ca51275c9d3359abd8385065a78c803b8 Mon Sep 17 00:00:00 2001 From: Vladimir Rutsky Date: Fri, 14 Oct 2016 16:15:59 +0400 Subject: [PATCH] fix typo: "certifcate" --- docs/container_registry.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/container_registry.md b/docs/container_registry.md index bd104988..3c593a5f 100644 --- a/docs/container_registry.md +++ b/docs/container_registry.md @@ -157,17 +157,17 @@ services: ## Generating certificate for authentication with the registry -So GitLab handles for us the authentication with Registry we need an certifcate to do that secure. +So GitLab handles for us the authentication with Registry we need an certificate to do that secure. With have here two options: 1. Use a signed certificate from an Trusted Certificate Authority. 2. Self-Signed Certificate for the authentication process. -### Signed Certifcate +### Signed Certificate If you have a signed certificate from a Trusted Certificate Authority you need only to copy the files in then `certs` folder and mount the folder in both containers (gitlab,registry) like in the docker-compose example. After that you need to set an environment variable in each container. In the **GitLab Container** you need to set `GITLAB_REGISTRY_KEY_PATH` this is the private key of the signed certificate. -In the **Registry Container** you need to set `REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE` to the certificate file of the signed certifcate. +In the **Registry Container** you need to set `REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE` to the certificate file of the signed certificate. For more info read [token auth configuration documentation][token-config]. ### Self Signed Certificate