ENCLAVR DOCS

Update a Caddy mask and directory

The complete Caddyfile is a protected namespace document selected by the host's caddy_mask_proxy.config_ref. The landing page is rendered during the Caddy deployment action from that document and the namespace's declared services and extra links.

  1. Locate the owner host and selected Caddy document in the authoritative assets. Confirm that the Caddy proxy is enabled on that host.
  2. Edit the protected document with ./enclavr priv edit --namespace <namespace> --component caddy-mask, using the repository's attended writer workflow. Preserve existing global options, access policy, TLS settings, and routes.
  3. Add or change the HTTPS site block. Browser-facing site addresses in the Caddyfile are collected into the namespace directory at the next Caddy deployment. www aliases share their primary site's card. Use web_directory.links for interfaces that have no Caddy site block.
  4. Review and push the complete document with the normal enclavr priv push workflow. Check its value-free plan before confirming a write.
  5. Deploy on the Caddy owner host: ./enclavr host deploy --only caddy-mask-proxy.deploy --yes.
  6. Verify Caddy configuration, container health, DNS, TLS, the directory page, and the destination from an appropriate client. The directory status dot means configured; it is not a live reachability test.

For the public docs.enclavr.io route, point the protected Caddy site block at docs:8080 on the Caddy mask Compose network. Do not import the private directory access policy for that public block.