Cloudflare DNS, Caddy and GitHub Pages

The portal hostname points to the existing VPS. Add only the dedicated block supplied in deploy/Caddyfile.fragment. Back up the current Caddyfile, run caddy validate --config /etc/caddy/Caddyfile, and reload only if validation succeeds. Check unrelated routes afterward. Caddy serves the portal and routes the exact authenticated ingestion path separately.

The wiki is a normal repository deployed by GitHub Actions to GitHub Pages. Set its publishing source to GitHub Actions and custom domain to raspberry.wiki.ramideltoro.com. Verify domain ownership where available. Configure the domain in Pages before creating its DNS record to reduce takeover risk.

Type	Name	Target	Proxy
CNAME	raspberry.wiki	ramideltoro.github.io	DNS only

The target is the account hostname, excluding the repository name. Astro’s site URL uses the custom HTTPS hostname and root base path. GitHub Actions ignores a repository CNAME file; configure the custom domain through Pages settings.

Standard Cloudflare Universal SSL does not cover this nested subdomain. Keep the wiki DNS-only and let GitHub Pages terminate TLS. Enable HTTPS enforcement after issuance; this may require waiting for the provider. Validate deep links, assets, search, cross-site links and the 404 page.

Sources: GitHub custom domain management, Cloudflare Universal SSL limitations.