docs: secret-file changes need a recreate; mergerfs passes inotify #380
No reviewers
Labels
No labels
audit-work
bug
docs
general-admin
major-upgrade
needs-vps-sync
new-service
on-hold
outside-work
post-podman
renovate
upstream
vps
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mysticalsoap/docker!380
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/secret-reload-mergerfs-inotify"
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?
Problem
Two constraints met during #376 that nothing documented: a replaced secret file is not picked up by
just up(compose tracks the path, not the content), and the mergerfs mount's inotify behaviour was undocumented, so the common "disable watchers on FUSE" advice looked applicable.Fix
One sentence each on the page that owns the concern: Secrets.md § Pattern 1 (recreate after changing a value), Home-Server.md § mergerfs (inotify works for writers through the mount, only direct branch writes are invisible).
Verification
Both observed live on 2026-10-07: Authelia stayed on the old
audiobookshelfclient secret afterjust up infraand loaded the new one onjust recreate authelia; a file created by thebookshelf-audiocontainer through/dataproduced create and delete inotify events for a watcher on/srv/media/...and inside theaudiobookshelfcontainer.🤖 Generated with Claude Code