From fdb1abd387eec05220a79db647859d788eddd8e2 Mon Sep 17 00:00:00 2001 From: ollypom Date: Fri, 10 Jan 2020 12:39:40 +0000 Subject: [PATCH] Added Nginx Recipe Redirect --- docs/recipes/nginx.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/recipes/nginx.md b/docs/recipes/nginx.md index b3f85ea9f..d66cf7fee 100644 --- a/docs/recipes/nginx.md +++ b/docs/recipes/nginx.md @@ -2,6 +2,8 @@ description: Restricting access to your registry using a nginx proxy keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, authentication, TLS, recipe, advanced title: Authenticate proxy with nginx +redirect_from: +- /registry/nginx/ --- ## Use-case @@ -40,8 +42,8 @@ proxy itself. > **Note**: Docker does not recommend binding your registry to `localhost:5000` without > authentication. This creates a potential loophole in your Docker Registry security. -> As a result, anyone who can log on to the server where your Docker Registry is running -> can push images without authentication. +> As a result, anyone who can log on to the server where your Docker Registry is running +> can push images without authentication. Furthermore, introducing an extra http layer in your communication pipeline makes it more complex to deploy, maintain, and debug. Make sure the extra