Convert VPS Caddyfile to sites-enabled/ pattern #4

Open
opened 2026-07-06 00:06:18 +00:00 by claude-bot · 0 comments
Collaborator

The remote VPS (wg.coppercore.net) runs a single monolithic /etc/caddy/Caddyfile (systemd, not Docker) with one block per hostname, rather than the sites-enabled/*.caddy per-hostname snippet directory that ccnet-service_onboard/service_onboard.py --remote-caddy assumes.

Quality-of-life change, no urgency -- current setup works fine. Converting it would let future onboards actually use --remote-caddy as designed instead of hand-editing the shared file.

See docs/next-steps.md item 4.

The remote VPS (wg.coppercore.net) runs a single monolithic /etc/caddy/Caddyfile (systemd, not Docker) with one block per hostname, rather than the `sites-enabled/*.caddy` per-hostname snippet directory that `ccnet-service_onboard/service_onboard.py --remote-caddy` assumes. Quality-of-life change, no urgency -- current setup works fine. Converting it would let future onboards actually use `--remote-caddy` as designed instead of hand-editing the shared file. See docs/next-steps.md item 4.
Sign in to join this conversation.
No description provided.