diff --git a/Deployment.md b/Deployment.md
index 2182a44..6a7519a 100644
--- a/Deployment.md
+++ b/Deployment.md
@@ -62,23 +62,8 @@ services:
 We recommend that you deploy TLS.
 There are several possibilities to do that.
 Because every setup is different and because TLS always requires 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:
-        - 8000:8080
-  ```
-  The target address for the reverse-proxy would in that case be `localhost:8000`.
-- 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`.
-> NOTE: From **version 0.28.0** and above the `nginx` service is no longer in use. The traffic must be forwarded to the `netbox` service directly.
+Learn more on [the dedicated _TLS_ wiki page](https://github.com/netbox-community/netbox-docker/wiki/TLS).
 
 ## Community-maintained Deployments