From ebf521007d18b33944294fa3819907a8e8f50321 Mon Sep 17 00:00:00 2001 From: dtoro Date: Sat, 6 Jun 2026 14:17:12 +0200 Subject: [PATCH] docs: emphasize Caddyfile must be edited via dtoro/caddy-conf repo, not directly on LXC --- operations/commands.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/operations/commands.md b/operations/commands.md index 2bfb60e..ddd8cdc 100644 --- a/operations/commands.md +++ b/operations/commands.md @@ -26,9 +26,11 @@ Run from the [hubris host](../hosts/hubris.md) as root. When working from `/root ## Reverse proxy -- Caddyfile: `/etc/caddy/Caddyfile` on [LXC 121](../containers/121-caddy.md). Tracked in `dtoro/caddy-conf`. Edits should be committed + pushed — see [auto-deploy](../infrastructure/auto-deploy.md). +- Caddyfile: `/etc/caddy/Caddyfile` on [LXC 121](../containers/121-caddy.md). +- **CRITICAL:** This file is tracked in `dtoro/caddy-conf` (https://git.hubris.network/dtoro/caddy-conf). Never edit it directly on the LXC — commit + push to the repo instead. Caddy auto-deploys on push (see [auto-deploy](../infrastructure/auto-deploy.md)). If you edit directly, the change will be lost on the next pull and agents won't know about it. - Hot reload: `pct exec 121 -- systemctl reload caddy`. - Validate: `pct exec 121 -- caddy validate --config /etc/caddy/Caddyfile`. +- Git workflow shortcut: `pct exec 121 -- "cd /etc/caddy && git add Caddyfile && git commit -m '...' && git push"`. ## DNS