docs(portainer): fix stale portainer.wbd-rd.nl refs (vhost is ops.wbd-rd.nl)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
znetsixe
2026-05-21 16:48:48 +02:00
parent f69453df99
commit c91b475cd1
2 changed files with 2 additions and 2 deletions

View File

@@ -4,7 +4,7 @@ Docker container management UI — the "operator console" for cloud and edge.
## Access ## Access
Portainer ingresses through nginx-proxy: `https://portainer.wbd-rd.nl/`. No host port is published by default. Portainer ingresses through nginx-proxy: `https://ops.wbd-rd.nl/`. No host port is published by default.
For emergency ops (nginx down, etc.), uncomment the `ports:` block in `compose.yml` and `docker compose up -d portainer` to expose `:9443` and `:8000` directly. For emergency ops (nginx down, etc.), uncomment the `ports:` block in `compose.yml` and `docker compose up -d portainer` to expose `:9443` and `:8000` directly.

View File

@@ -1,6 +1,6 @@
# portainer — container management UI (operator console) # portainer — container management UI (operator console)
# Networks: mgmt (docker socket plane) + app (nginx-proxy reaches HTTPS upstream) # Networks: mgmt (docker socket plane) + app (nginx-proxy reaches HTTPS upstream)
# Ingress: nginx-proxy → portainer:9443 (self-signed upstream cert) → portainer.wbd-rd.nl # Ingress: nginx-proxy → portainer:9443 (self-signed upstream cert) → ops.wbd-rd.nl
# #
# Direct :9443 host access is intentionally NOT published anymore — re-enable # Direct :9443 host access is intentionally NOT published anymore — re-enable
# only for emergency ops by uncommenting the `ports:` block below. # only for emergency ops by uncommenting the `ports:` block below.