From 59b34bfd860286a6f4a72dc5fec2c5f626542ac2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20M=C3=A4der?= Date: Tue, 17 Mar 2020 15:45:36 +0100 Subject: [PATCH] Updated Deployment (markdown) --- Deployment.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/Deployment.md b/Deployment.md index 180103a..800d198 100644 --- a/Deployment.md +++ b/Deployment.md @@ -57,6 +57,28 @@ services: restart: unless-stopped ``` +### TLS (HTTPS) + +We recommend that you deploy TLS. +There are several possibilities to do that. +Because the every setup is different and because TLS always required a domain there is no built-in solution. +Our recommendations: + +- Deploy a HTTP server on your host system and reverse-proxy to the Netbox Nginx container. + Configure TLS on that daemon. + Make sure that you specify a fixed port in your `docker-compose.override.yml` file for the nginx service, like so: + ```yaml + version: '3.4' + services: + nginx: + ports: + - 8080:8080 # binds nginx to `localhost:8080` on the host server + ``` + The target address for the reverse-proxy would in that case be `localhost:8080`. +- Deploy an HTTP server through Docker. + You can extend the base setup via the `docker-compose.override.yml` file. + The target server for the reverse proxy would be `nginx:8080`. + ## Community-maintained Deployments * [Helm Chart][netbox-helm] by @bootc