fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record Serenity DB dependency mapping
Some checks failed
secret-guardrails / gitleaks (push) Has been cancelled
Details
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-25 22:40:10 +00:00
parent 90027f9fa7
commit b6bb040de6
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/planning/SERENITY_CLEANUP_WAVE_1.md
View File

@@ -61,6 +61,7 @@ From the live Serenity audit:
- ARR/torrent locality is still tied to `/mnt/user/data`
- `GameVault` points at local Postgres on `10.5.30.5:5432`
- `RomM` points at local MariaDB on `10.5.30.5:3306`
- live container env inspection still shows those explicit DB_HOST/DB_PORT bindings on 2026-05-25
- quick live checks did not surface immediate DB dependencies for `Wizarr`, `Shelfmark`, or `Notifiarr`
- `Newt` is still needed
- legacy Pi-hole containers are still running even though Technitium is now the intended DNS path
@@ -235,6 +236,7 @@ Recommended sequence:
Default recommendation:
- prefer PD shared-postgres unless GameVault has a proven reason to stay isolated
- note: live `psql` inspection on 2026-05-25 showed a Postgres collation-version mismatch warning on Serenity (`gamevault` created with glibc collation 2.36 while host now provides 2.41), so include a post-migration refresh/reindex plan rather than carrying that debt forward silently
### Pair 2: RomM + local MariaDB