Chris
33cab10cef
Syncs project memory, custom agents, and commands across machines. Excludes secrets (settings.json), session state, and runtime files. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
843 B
843 B
name, description, type
| name | description | type |
|---|---|---|
| Caddyfile edits must preserve inode | Python open().write() breaks Docker bind mounts by creating new inodes — use sed -i or tee instead | feedback |
Never edit the Caddyfile (or any Docker bind-mounted file) with Python's open(path, 'w').write() — it creates a new inode and Docker keeps reading the old one.
Why: Docker bind mounts track the original file inode. Python's write creates a new file, so caddy reload reads stale content. This caused hours of debugging where Caddy appeared to ignore config changes.
How to apply: Use sed -i for substitutions or cat newfile | tee /path/to/file > /dev/null for full rewrites. If the inode is already broken, restart the container (docker restart caddy) to re-mount. Always verify with docker exec caddy cat /etc/caddy/Caddyfile after edits.