Skip to content

docs: add Nextcloud AIO example - #564

Open
almeidapaulopt wants to merge 1 commit into
mainfrom
docs/nextcloud-aio-example
Open

almeidapaulopt wants to merge 1 commit into
mainfrom
docs/nextcloud-aio-example

Conversation

@almeidapaulopt

Copy link
Copy Markdown
Owner

What

Adds a dedicated Nextcloud AIO example page to the docs (v3 and v2), addressing the confusion from #560: port 8080 is the nextcloud-aio-mastercontainer setup UI (to be opened by IP, per upstream — HSTS blocks domain access later), while Nextcloud itself is served by nextcloud-aio-apache on APACHE_PORT (11000, the upstream sample).

  • New pages: docs/content/docs/v3/examples/nextcloud-aio.md and docs/content/docs/examples/nextcloud-aio.md, cross-linked from both Nextcloud pages (nav weights updated).
  • Compose + labels for the standard AIO flow: since the Apache container is created by the mastercontainer (upstream explicitly warns custom Docker labels/env on it are not possible), the tsdproxy labels go on the mastercontainer: tsdproxy.port.1: "443/https:11000/http". tsdproxy then targets the host-published APACHE_PORT via host.docker.internal (the explicit-port-label fallback, present on both main and v2.3.4).
  • The AIO interface is mapped as 8081:8080 (only the host port may change, upstream-documented) so it no longer collides with the tsdproxy dashboard — the exact port conflict reported in the issue.
  • Notes cover: APACHE_IP_BINDING must stay 0.0.0.0 (loopback blocks host.docker.internal), SKIP_DOMAIN_VALIDATION=true for tailnet-only .ts.net names (upstream's documented escape hatch), and why OVERWRITEPROTOCOL/trusted-domain tweaks from the plain-image example don't apply.
  • Alternative section for AIO's manual installation, where users own the compose and can label nextcloud-aio-apache directly — tsdproxy then reaches it over the Docker network with no published ports.

Closes #560

Verification

Upstream facts checked against nextcloud/all-in-one main (README.md, reverse-proxy.md, manual-install/readme.md, compose.yaml, php/src/Docker/DockerActionManager.php — the fixed sibling-container label set) — no invented ports or container names.

Following the #561 approach, a throwaway harness extracted every tsdproxy.yaml fence in docs/content/docs and loaded it through the strict loader (config.NewConfigFile(...).Load(), the unmarshalNormalized path), and validated every tsdproxy.port.N value through model.NewPortLongLabel + the option set:

  • All fences and labels in the touched/related example pages pass (v3 nextcloud.md, nextcloud-aio.md, grafana pages, v2 AIO labels incl. the redirect form with the <tailnet-name> placeholder).
  • The run flags pre-existing issues in pages this PR does not touch (e.g. getting-started.md dashboard: — the target of the still-open docs: fix invalid server config examples (dashboard section, proxyAccessLog placement) #561 — plus range-syntax labels that go through ExpandPortRangeLabel, and roadmap/aspirational options). Left alone to keep this PR docs-example scoped.
  • hugo build passes; both new pages render with the cross-links resolved.

Nextcloud AIO serves Nextcloud from the nextcloud-aio-apache container
on APACHE_PORT, not from port 8080 (the mastercontainer setup UI, which
upstream says to open by IP only). The Apache container is created by
the mastercontainer, so it cannot carry TSDProxy labels - the example
labels the mastercontainer and forwards to the host-published APACHE_PORT.

- new v3 + v2 example pages (compose, labels, access, notes)
- mastercontainer flow plus the manual-install alternative (labels on
  nextcloud-aio-apache, Docker-network access, no published ports)
- cross-links from the Nextcloud pages, nav weights updated

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using port 8080:8080 for NextCloud blocks setup page

1 participant