coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record verified Forgejo Scaleway backup and recovery
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-06 01:03:02 +02:00
parent be45c4e3fd
commit 4a9d6e6c7f
8 changed files with 114 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

9
SCOPE.md
View file

@ -56,7 +56,7 @@ replacement entry points; source files are not deleted merely to tidy scope.
## Work that closes the intent gaps
The [current work index](workplans/README.md) groups six open workplans.
The [current work index](workplans/README.md) groups seven open workplans.
The [full assessment](history/2026-09-05-platform-intent-workplan-assessment.md)
records every reviewed plan and the consolidation mapping.
@ -137,12 +137,15 @@ remain RPF-WP-0029-T02. See the
Scaleway Standard Multi-AZ (`nl-ams`) is the primary backup destination under
RESOURCE-WP-0002. Nextcloud is the independent secondary-copy lane. The live
Scaleway paths cover apps-pg, platform-pg and platform-pg-2. An isolated apps-pg
Scaleway paths cover apps-pg, platform-pg, platform-pg-2 and forgejo-db. An isolated apps-pg
restore from that primary succeeded in 42.64 seconds; production remained ready
and scratch resources were removed. See
[primary recovery evidence](docs/evidence/scaleway-primary-restore-2026-09-06.json).
Coverage is per asset: live forgejo-db, net-kingdom-pg and state-hub-db have no
Forgejo native primary backup and isolated recovery now pass (45.08 seconds;
142 repository records, six users, 2,040 package blob records). See
[Forgejo primary evidence](docs/evidence/forgejo-scaleway-restore-2026-09-06.json).
Coverage is per asset: net-kingdom-pg and state-hub-db still have no observed
native Barman destination. The Forgejo full-archive helper still targets
Nextcloud; no Forgejo blob/archive destination on Scaleway was evidenced.
The account cutover and archive-integrity fix do not establish that coverage.