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

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

View file

@ -4,7 +4,7 @@ type: workplan
title: "Close Forgejo primary backup coverage on Scaleway"
domain: financials
repo: railiance-platform
status: active
status: blocked
owner: codex
created: "2026-09-06"
updated: "2026-09-06"
@ -35,7 +35,7 @@ server directory. Retention follows the existing 30-day primary contract.
```task
id: RPF-WP-0038-T02
status: progress
status: done
priority: high
state_hub_task_id: "b6960c2e-1ad3-5c23-bfb6-9f1f16d0f0c2"
```
@ -45,11 +45,15 @@ base backup. Apply only the reviewed backup field with a resource-version
guard, preserving unrelated live settings. Require a completed fresh Backup,
continuous archiving and source readiness; record metadata only.
Completed: fresh backup `forgejo-db-daily-20260905225013`, backup ID
`20260905T225115`, source Ready and continuous archiving healthy. Evidence:
`docs/evidence/forgejo-scaleway-activation-2026-09-06.json`.
## Prove isolated primary database recovery
```task
id: RPF-WP-0038-T03
status: todo
status: done
priority: high
state_hub_task_id: "b47b5905-83c8-5da8-9951-e8cb7b7459f9"
```
@ -59,6 +63,10 @@ Verify expected Forgejo database and nonempty repository/user/package metadata,
source readiness and scratch cleanup. This is database recovery, not combined
Forgejo blob/application recovery.
Completed: restored in 45.08 seconds, 142 repository records, six users and
2,040 package blob records. Production remained Ready; scratch namespace
removed. Evidence: `docs/evidence/forgejo-scaleway-restore-2026-09-06.json`.
## Establish primary full-archive delivery and application recovery
```task