From 661f7b49b34e540d1affcdddd7bbebd664ffbe8f Mon Sep 17 00:00:00 2001 From: Fizzlepoof Date: Mon, 25 May 2026 23:26:55 +0000 Subject: [PATCH] docs: require final quiesced Serenity DB export --- docs/planning/SERENITY_CLEANUP_WAVE_1.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/planning/SERENITY_CLEANUP_WAVE_1.md b/docs/planning/SERENITY_CLEANUP_WAVE_1.md index 2c3c06a..921d4cf 100644 --- a/docs/planning/SERENITY_CLEANUP_WAVE_1.md +++ b/docs/planning/SERENITY_CLEANUP_WAVE_1.md @@ -375,10 +375,12 @@ Definition of done: ### Card D3 — export and validate Serenity source databases Definition of done: +- pre-cutover exports from Serenity are taken for both apps so restore/import flow can be tested before downtime - `gamevault` Postgres dump exported from Serenity and integrity-checked - `romm` MariaDB dump exported from Serenity and integrity-checked - source app versions and DB container versions recorded alongside dumps - Postgres collation-version warning captured as a post-import remediation item +- final cutover note recorded: these pre-cutover dumps are not the authoritative final state; a last quiesced export must be taken after the Serenity app is stopped during cutover and imported to PD before PD goes live ### Card D4 — sync appdata for GameVault and RomM to PD staging paths Definition of done: @@ -390,6 +392,7 @@ Definition of done: ### Card D5 — cut over GameVault to PD Definition of done: - Serenity GameVault stopped only for the final cutover window +- after GameVault is stopped on Serenity, a final quiesced `gamevault` Postgres export is taken and imported to the PD target DB so PD does not come up on stale data - PD GameVault starts against the PD target Postgres DB - login, library visibility, metadata behavior, and save/upload paths verified - public/LAN route updated if needed and verified @@ -398,6 +401,7 @@ Definition of done: ### Card D6 — cut over RomM to PD Definition of done: - Serenity RomM stopped only for the final cutover window +- after RomM is stopped on Serenity, a final quiesced `romm` MariaDB export is taken and imported to the PD target DB so PD does not come up on stale data - PD RomM starts against the PD target MariaDB DB - UI, library visibility, assets/resources, background jobs, and metadata behavior verified - public/LAN route updated if needed and verified