From b6bb040de616c682a5f24203a76d8b45649922f3 Mon Sep 17 00:00:00 2001 From: Fizzlepoof Date: Mon, 25 May 2026 22:40:10 +0000 Subject: [PATCH] docs: record Serenity DB dependency mapping --- docs/planning/SERENITY_CLEANUP_WAVE_1.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/planning/SERENITY_CLEANUP_WAVE_1.md b/docs/planning/SERENITY_CLEANUP_WAVE_1.md index 430b0e9..1e7096d 100644 --- a/docs/planning/SERENITY_CLEANUP_WAVE_1.md +++ b/docs/planning/SERENITY_CLEANUP_WAVE_1.md @@ -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