The docs_site nginx container is the stock image and does not know it is behind Traefik/Cloudflare, so its directory redirect is absolute and scheme-blind: GET https://offloaded.dev/docs -> 301 Location: http://offloaded.dev/docs/. Only the no-trailing-slash form hits it and MkDocs emits trailing-slash links, so navigation never goes through it. Fix: absolute_redirect off in the container config (relative Location), costs a container recreate, hence not urgent. Introduced with the /docs mount deploy.
Imported from beads archie-core-mnpj · GitHub #1163 · type chore · priority P3 · created 2026-09-22
The docs_site nginx container is the stock image and does not know it is behind Traefik/Cloudflare, so its directory redirect is absolute and scheme-blind: GET https://offloaded.dev/docs -> 301 Location: http://offloaded.dev/docs/. Only the no-trailing-slash form hits it and MkDocs emits trailing-slash links, so navigation never goes through it. Fix: absolute_redirect off in the container config (relative Location), costs a container recreate, hence not urgent. Introduced with the /docs mount deploy.
---
_Imported from beads `archie-core-mnpj` · GitHub #1163 · type chore · priority P3 · created 2026-09-22_
Triaged: no code change is needed for this. The defect is real but not fixable in sam/archie. This repository has no docs_site nginx container, no Traefik/Cloudflare front, and no /docs mount: there are no *.conf files and no matches for nginx, Traefik, proxy_pass, server_name or absolute_redirect anywhere in the tree (the only "Traefik" hit is a comment in deployments/docker-nats-stack.toml about archied trusting X-Forwarded-Proto, an unrelated service). docker-compose.yml defines only postgres, nats, agent and agent-net; .github/workflows/deploy.yml builds only archied, archie-agent and the distribution zip; no mkdocs config exists and no Go code serves /docs. docs/ here is content source (docs/prds, docs/guides, docs/news/releases.json+redirects.json written by tools/newsgen), and the site is served from https://offloaded.dev by a container whose config lives outside this checkout. The stated fix — absolute_redirect off in that container's nginx config — is a one-line config change plus a container recreate, but it has to be made in whichever repo/host owns the docs_site container. Recommend moving #1449 to that infra repo rather than building anything here. Two other grounds for closing it outright: the issue itself notes MkDocs emits trailing-slash links, so no navigation actually reaches the scheme-blind 301, and it is filed P3 "not urgent" — the visible impact today is a manual https://offloaded.dev/docs request landing on http://. If the maintainer confirms the infra repo and wants the tweak, its shape is already settled (single config directive, well-understood), so implement would be the right workflow there — not feasibility, since there is no design question to settle.
Triaged: no code change is needed for this. The defect is real but not fixable in sam/archie. This repository has no docs_site nginx container, no Traefik/Cloudflare front, and no /docs mount: there are no *.conf files and no matches for nginx, Traefik, proxy_pass, server_name or absolute_redirect anywhere in the tree (the only "Traefik" hit is a comment in deployments/docker-nats-stack.toml about `archied` trusting X-Forwarded-Proto, an unrelated service). docker-compose.yml defines only postgres, nats, agent and agent-net; .github/workflows/deploy.yml builds only archied, archie-agent and the distribution zip; no mkdocs config exists and no Go code serves /docs. docs/ here is content source (docs/prds, docs/guides, docs/news/releases.json+redirects.json written by tools/newsgen), and the site is served from https://offloaded.dev by a container whose config lives outside this checkout. The stated fix — `absolute_redirect off` in that container's nginx config — is a one-line config change plus a container recreate, but it has to be made in whichever repo/host owns the docs_site container. Recommend moving #1449 to that infra repo rather than building anything here. Two other grounds for closing it outright: the issue itself notes MkDocs emits trailing-slash links, so no navigation actually reaches the scheme-blind 301, and it is filed P3 "not urgent" — the visible impact today is a manual `https://offloaded.dev/docs` request landing on http://. If the maintainer confirms the infra repo and wants the tweak, its shape is already settled (single config directive, well-understood), so `implement` would be the right workflow there — not feasibility, since there is no design question to settle.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The docs_site nginx container is the stock image and does not know it is behind Traefik/Cloudflare, so its directory redirect is absolute and scheme-blind: GET https://offloaded.dev/docs -> 301 Location: http://offloaded.dev/docs/. Only the no-trailing-slash form hits it and MkDocs emits trailing-slash links, so navigation never goes through it. Fix: absolute_redirect off in the container config (relative Location), costs a container recreate, hence not urgent. Introduced with the /docs mount deploy.
Imported from beads
archie-core-mnpj· GitHub #1163 · type chore · priority P3 · created 2026-09-22Triaged: no code change is needed for this. The defect is real but not fixable in sam/archie. This repository has no docs_site nginx container, no Traefik/Cloudflare front, and no /docs mount: there are no *.conf files and no matches for nginx, Traefik, proxy_pass, server_name or absolute_redirect anywhere in the tree (the only "Traefik" hit is a comment in deployments/docker-nats-stack.toml about
archiedtrusting X-Forwarded-Proto, an unrelated service). docker-compose.yml defines only postgres, nats, agent and agent-net; .github/workflows/deploy.yml builds only archied, archie-agent and the distribution zip; no mkdocs config exists and no Go code serves /docs. docs/ here is content source (docs/prds, docs/guides, docs/news/releases.json+redirects.json written by tools/newsgen), and the site is served from https://offloaded.dev by a container whose config lives outside this checkout. The stated fix —absolute_redirect offin that container's nginx config — is a one-line config change plus a container recreate, but it has to be made in whichever repo/host owns the docs_site container. Recommend moving #1449 to that infra repo rather than building anything here. Two other grounds for closing it outright: the issue itself notes MkDocs emits trailing-slash links, so no navigation actually reaches the scheme-blind 301, and it is filed P3 "not urgent" — the visible impact today is a manualhttps://offloaded.dev/docsrequest landing on http://. If the maintainer confirms the infra repo and wants the tweak, its shape is already settled (single config directive, well-understood), soimplementwould be the right workflow there — not feasibility, since there is no design question to settle.