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

Verify Scaleway primary recovery and distinguish secondary backup coverage
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
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 00:34:43 +02:00
parent 9269d9d8f4
commit d05c3000c5
10 changed files with 170 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/forgejo-backup.md
View file

@ -1,6 +1,12 @@
# Forgejo backup (railiance01)
Workplan: `RAIL-HO-WP-0005` T04/T09 · Decision: Option A (Nextcloud + age)
Workplan: `RAIL-HO-WP-0005` T04/T09 · Secondary copy: Nextcloud + age
Scaleway is the platform primary backup provider. This helper currently writes
Forgejo archives only to Nextcloud. Live inspection on 2026-09-06 found no
Barman destination on forgejo-db and no reviewed Scaleway blob/archive path.
Treat Forgejo primary coverage as a gap; primary service selection alone does
not prove each asset has migrated.
## What is backed up