mirror of
https://github.com/netbox-community/netbox-docker.git
synced 2025-06-09 03:26:40 +02:00
Updated Deployment (markdown)
parent
0604c5d4a5
commit
59b34bfd86
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user