Documentation · Websites
Website management
Register static sites and loopback application proxies, retain immutable revisions and publish deployment fragments through explicit background jobs.
Website definitions
A managed website has a name, one or more unique domains and either a static document root inside Warden's filesystem boundary or an HTTP(S) loopback upstream. Restricting proxy upstreams to loopback preserves the same local reverse-proxy boundary used by Warden itself.
Immutable revisions
Every save creates a complete JSON revision of the website definition. Updates carry the revision they were edited from; a stale browser cannot silently overwrite a newer save and must reload first. Current state remains convenient to query while revision history preserves what configuration existed at each change.
Publish jobs
Publishing queues an operation rather than hiding filesystem work inside the form request. The worker re-resolves static roots, quotes Caddy directive values, atomically replaces the fragment under sites/, and records queued, running, completed or failed state with a result message.
Deliberate deployment boundary
Include Warden's generated fragment directory from a Caddy configuration you control, then validate and reload Caddy through your normal deployment process. This keeps Warden from unexpectedly taking ownership of an existing reverse proxy.