gtiandClaude Sonnet 5
096f201c84
--env-file only feeds the containers; a plain shell script never saw BACKUP_DIR, so it silently fell back to ./backups while the Hub itself used the real value from .env. Found in production: postgres's /backups bind mount was still pinned to a directory orphaned by an earlier git-archive swap (mv gti-fiscal gti-fiscal_old && mv gti-fiscal_new gti-fiscal — Linux bind mounts follow the original dentry, not the path string), so every backup.sh run had been silently landing dumps nobody could find at the live path. Fixed by pointing BACKUP_DIR at a stable absolute path outside the deploy tree and recreating postgres once to pick it up; verified with a real ./backup.sh run in production. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>