adding some lines
All checks were successful
deploy-docs / build-and-deploy (push) Successful in 1m19s
All checks were successful
deploy-docs / build-and-deploy (push) Successful in 1m19s
This commit is contained in:
@@ -32,6 +32,8 @@ configurations.
|
||||
{{% include "/srv/configs/docker_compose/nginx-proxy-manager/docker-compose.yaml" %}}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Automation (Docker Labels)
|
||||
|
||||
To avoid manually configuring Proxy Hosts in the UI (and to keep configuration tightly coupled with the services themselves), I use the `npm-sync` sidecar container.
|
||||
@@ -56,6 +58,8 @@ services:
|
||||
> [!important] Direct Edits
|
||||
> Avoid making direct edits to NPM `.conf` files on the host, as it will desync the database and the Web UI. Always use the Web UI or API-driven automation like `npm-sync`.
|
||||
|
||||
---
|
||||
|
||||
## Nginx routing
|
||||
|
||||
Nginx gives you that great routing to your internal networked servers. Also
|
||||
@@ -72,6 +76,8 @@ all traffic to nginx. Then based on some rules I have set up I can point that
|
||||
traffic to my internal server. For this I will need a domain name server (DNS)
|
||||
to point to my external IP.
|
||||
|
||||
---
|
||||
|
||||
## DNS
|
||||
|
||||
A domain name server (DNS) allows me to make a name that can be easily looked up
|
||||
@@ -172,3 +178,5 @@ Use https here only if you have ssl setup on your origin server and your server
|
||||
is set up to accept https, otherwise you make get bad gateway 502 errors.
|
||||
|
||||

|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user