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

docs: require final quiesced Serenity DB export
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-25 23:26:55 +00:00
parent de188e6047
commit 661f7b49b3
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/planning/SERENITY_CLEANUP_WAVE_1.md
View File

@@ -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