coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/history/2026-09-06-backup-problem-followup.md
codex 4a9d6e6c7f
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Record verified Forgejo Scaleway backup and recovery 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
2026-09-06 01:03:02 +02:00

1.9 KiB
Raw Blame History

Backup problem follow-up — 2026-09-06

The attended-login failures were caused by missing Linux browser launchers on this WSL host. The installed Bao browser dependency tries xdg-open, x-www-browser and www-browser; none was installed. The unauthenticated OIDC routing probe returned the expected Keycloak host and localhost callback. Implemented a narrowly validated, repository-scoped Windows browser bridge and retained Warden's contained credential session. The replacement login reached the silent owner command and began the real secondary archive transfer. Transfer and revocation results are recorded separately when complete.

Forgejo's native PostgreSQL backup is now active on the primary Scaleway bucket at platform-pg/forgejo-db/, using the existing CCR-2026-0012 backup identity. No IAM expansion or new credential delivery was needed. A resource-version guarded patch changed only the live backup field; source manifests include HTTPS/DNS egress, daily 02:35 UTC base backup, WAL archiving and 30-day retention. The fresh backup completed with production Ready and continuous archiving.

An isolated Scaleway recovery became ready in 45.08 seconds and preserved 142 repository records, six users and 2,040 package blob records. Production remained Ready and the scratch namespace was removed. These are database records, not recovered repository/package files. WP-0038-T01/T02/T03 are done. T04 retains the separate full-archive primary delivery and application recovery contract; WP-0029 retains the secondary incident and predecessor invalidation.

Evidence:

  • docs/evidence/forgejo-scaleway-activation-2026-09-06.json
  • docs/evidence/forgejo-scaleway-restore-2026-09-06.json

All 204 repository tests passed after the browser fix and generalized primary restore helper. The live primary recovery additionally verified that helper against the new Forgejo Barman destination.