Feedback media server deploy bind mount

When deploying to media-server CT 102 via the tar-based deploy.sh, files that are bind-mounted into nginx by file path (e.g. nginx-default.conf) get orphaned after tar replaces them on disk. The nginx daemon inside the container keeps the old inode open, so nginx -s reload silently runs on the old config.

Why: Docker bind-mount-by-file pins the inode at container start. Tar-replace creates a new inode; the running process never sees it. Bind-mount-by-directory does not have this problem because the directory inode stays stable.

How to apply: After any deploy that modifies nginx config files on CT 102, run a container restart (docker restart justinandkrystal-landing or the relevant container), not just an nginx reload. If a config change appears to not take effect after deploy, check for this first.

[auto-memory session e0097de0-7e40-40e5-8991-c9d652aef72a, confidence 0.75, mode staged]