From d368f45c972e28a05c62d588ea32ca5a7390d354 Mon Sep 17 00:00:00 2001 From: Tobias Genannt Date: Tue, 3 Feb 2026 11:57:04 +0100 Subject: [PATCH] Updated TLS (markdown) --- TLS.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/TLS.md b/TLS.md index 621430f..eaf044a 100644 --- a/TLS.md +++ b/TLS.md @@ -5,11 +5,6 @@ But we recommend setting up a reverse proxy that is independent of the NetBox Do You can do this by installing a webserver like _nginx_ on your host machine directly (and forward all traffic to the container) or by running such a webserver in a container, [as explained below on the example of _Caddy_](#tls-using-caddy-container). -**We strongly advise _against_ changing the Nginx Unit configuration that ships with NetBox Docker.** -The reason is that we don't see the internal configuration as part of the "user interface" and therefore we change it whenever we think it's necessary. -Such changes may also not be mentioned in the release notes either. -So it would be up to you to keep your configuration in sync with what the NetBox Docker project comes up with. - ## TLS using _Caddy_ [Caddy](https://caddyserver.com/) is a powerful webserver written in Go and has many built-in features that make it the perfect fit for our case.