fix
BREAKING
fix/production-backups-r2-bucket
#1 / 1
fix: backup.sh targets the correct postgres container, wire BACKUP_R2_BUCKET through secrets.sh
- backup.sh used 'docker compose exec postgres', but production has no docker-compose.yml — fixed to 'docker exec musehub_postgres' directly - secrets.sh now fetches BACKUP_R2_BUCKET from SSM (plain String, optional) and writes it into .env so backup.sh's R2 upload path can find it
sha256:2894a51b97aa20cf06bd155f9929ff23b13b2eca0ab995a733f1f423228565e7
sha
+1
symbols
2 changed · 1059 in snapshot
files
sha256:2f771624609895567c93ac95623d4d4f5ddbf85fd6985ce398460ed1f7cb24b4
snapshot
+1
symbol added
2
files changed
1059
files in snapshot
0
dead code introduced
Semantic Changes
1 symbol
Files Changed
~2
1059 in snapshot
~2
1059 in snapshot
← Older
Oldest on fix/production-backups-r2-bucket
All commits
Newer →
Latest on fix/production-backups-r2-bucket
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:2894a51b97aa20cf06bd155f9929ff23b13b2eca0ab995a733f1f423228565e7 --body "your comment"
No comments yet. Be the first to start the discussion.