docs
patch
infra/database-phase2-production-rds
#1 / 1
docs: record Phase 2 completion -- production migrated to encrypted RDS
Provisioned musehub-production-db (encrypted at rest, deletion-protected, 7-day backups, VPC-scoped security group) in the Production AWS account. Migrated data via pg_dump/pg_restore (74 tables, 6 repos, 5 identities verified matching before cutover). Wired DATABASE_URL through SSM using the same secrets.sh mechanism built for staging in Phase 1. Redeployed and verified live via /healthz and a real repo-list API query.
Old self-hosted Postgres archived and stopped -- retained through a 2+ week safety window before decommissioning. Both staging and production are now on managed AWS RDS.
sha256:6bd33e7daa2d2c6de7216008ee3ccecdb5ad76d9ea7704744cd44fbd2646b7c1
sha
+1
~4
−1
symbols
1 changed · 1061 in snapshot
files
sha256:b8abf2a293b3f98407583fa705de9dfe77c3ce7c88dc871d4db9f21542a93d7e
snapshot
+1
symbol added
~4
symbols modified
−1
symbol removed
1
file changed
1061
files in snapshot
0
dead code introduced
Semantic Changes
6 symbols
+
.vscode/
+
alembic/
+
deploy/
+
docs/
+
musehub/
+
scripts/
+
src/
+
src/ts/
+
tests/
+
tools/
−
Phase 2 — Migrate production from self-hosted Postgres to RDS
section Phase 2 — Migrate production from self-hosted Postgres to RDS L143–156
+
Phase 2 — Migrate production from self-hosted Postgres to RDS — DONE 2026-09-08
section Phase 2 — Migrate production from self-hosted Postgres to RDS — DONE 2026-09-08 L147–181
~
table
Files Changed
~1
1061 in snapshot
~1
1061 in snapshot
← Older
Oldest on infra/database-phase2-production-rds
All commits
Newer →
Latest on infra/database-phase2-production-rds
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:6bd33e7daa2d2c6de7216008ee3ccecdb5ad76d9ea7704744cd44fbd2646b7c1 --body "your comment"
No comments yet. Be the first to start the discussion.