Repository navigation
docs: add Nextcloud AIO example - #564
Open
almeidapaulopt wants to merge 1 commit into
Open
almeidapaulopt wants to merge 1 commit into
almeidapaulopt wants to merge 1 commit into
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-mastercontainersetup UI (to be opened by IP, per upstream — HSTS blocks domain access later), while Nextcloud itself is served bynextcloud-aio-apacheonAPACHE_PORT(11000, the upstream sample).docs/content/docs/v3/examples/nextcloud-aio.mdanddocs/content/docs/examples/nextcloud-aio.md, cross-linked from both Nextcloud pages (nav weights updated).tsdproxy.port.1: "443/https:11000/http". tsdproxy then targets the host-publishedAPACHE_PORTviahost.docker.internal(the explicit-port-label fallback, present on both main and v2.3.4).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.APACHE_IP_BINDINGmust stay0.0.0.0(loopback blockshost.docker.internal),SKIP_DOMAIN_VALIDATION=truefor tailnet-only.ts.netnames (upstream's documented escape hatch), and whyOVERWRITEPROTOCOL/trusted-domain tweaks from the plain-image example don't apply.nextcloud-aio-apachedirectly — 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.yamlfence indocs/content/docsand loaded it through the strict loader (config.NewConfigFile(...).Load(), theunmarshalNormalizedpath), and validated everytsdproxy.port.Nvalue throughmodel.NewPortLongLabel+ the option set:nextcloud.md,nextcloud-aio.md, grafana pages, v2 AIO labels incl. the redirect form with the<tailnet-name>placeholder).getting-started.mddashboard:— the target of the still-open docs: fix invalid server config examples (dashboard section, proxyAccessLog placement) #561 — plus range-syntax labels that go throughExpandPortRangeLabel, and roadmap/aspirational options). Left alone to keep this PR docs-example scoped.hugobuild passes; both new pages render with the cross-links resolved.