SEQN Auth Docs Hosting

Public SEQN Auth docs should be hosted at:

https://docs.seqn.in

This is the confirmed public docs domain for SEQN Auth. The auth runtime stays on auth.seqn.in; Authentik stays on accounts.seqn.in.

DNS

Create one public DNS record before enabling the Caddy route:

docs.seqn.in A 80.225.246.45

If the DNS provider uses proxying/CDN mode, keep HTTPS passthrough compatible with Caddy automatic certificates. Do not point docs.seqn.in at auth.seqn.in; docs should be a separate host.

VPS layout

Use a static output directory outside the app containers:

/srv/silver-auth/docs-site/public

The directory can be populated by the repo docs builder:

npm run build:seqn-auth-docs

The builder reads docs/seqn-auth/*.md, writes static HTML into .tmp/seqn-auth-docs-site/public, gives every code block a readable dark surface, and adds a copy-code button. Publish that generated directory into /srv/silver-auth/docs-site/public and keep the repo Markdown as the source of truth.

Recommended ownership on the VPS:

sudo mkdir -p /srv/silver-auth/docs-site/public
sudo chown -R root:root /srv/silver-auth/docs-site
sudo chmod -R u=rwX,g=rX,o=rX /srv/silver-auth/docs-site

Caddy

Use services/silver-auth-api/deploy/docs-site.Caddyfile as the route template. If the VPS uses the existing shared Caddy proxy, copy the docs.seqn.in block into the active Caddyfile beside the accounts.seqn.in and auth.seqn.in blocks.

The route serves static files only and does not proxy to the Silver Auth API.

Deploy checklist

  • Generate static docs into /srv/silver-auth/docs-site/public.
  • If using the current shared Caddy container, also copy the generated files into croox-web-caddy-1:/srv/silver-auth/docs-site/public until the host directory is bind-mounted.
  • Add the docs.seqn.in Caddy block.
  • Reload Caddy after caddy validate passes.
  • Confirm https://docs.seqn.in/ loads over HTTPS.
  • Confirm missing pages do not expose directory listings.
  • Add external uptime monitoring for https://docs.seqn.in/.

Current blocker

Actual DNS creation and TLS verification require DNS-provider access for seqn.in. Until the docs.seqn.in record exists, this repository can only provide the hosting runbook and Caddy template.