Convert VPS Caddyfile to sites-enabled/ pattern #4
Labels
No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
copper/ccnet-prod-devops#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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/*.caddyper-hostname snippet directory thatccnet-service_onboard/service_onboard.py --remote-caddyassumes.Quality-of-life change, no urgency -- current setup works fine. Converting it would let future onboards actually use
--remote-caddyas designed instead of hand-editing the shared file.See docs/next-steps.md item 4.