docs: update documentation to OKF v0.1 format
This commit is contained in:
@@ -3,7 +3,7 @@ type: guide
|
||||
title: Admin — System (Backup, Restore, Danger Zone)
|
||||
description: How an admin navigates to /admin/system, creates a backup, stages and commits a restore, resets all scores, and wipes challenges — including the re-authentication confirmation, progress, and side effects.
|
||||
tags: [guide, admin, system, backup, restore, danger-zone, confirmation]
|
||||
timestamp: 2026-07-23T12:04:50Z
|
||||
timestamp: 2026-07-23T15:46:55Z
|
||||
---
|
||||
|
||||
# Navigation
|
||||
@@ -157,7 +157,13 @@ messages. Notable mappings:
|
||||
password, type `RESTORE BACKUP`, click **Confirm**.
|
||||
6. The modal closes, the page shows a brief *Restore complete.
|
||||
Logging out…* toast, and the SPA navigates to `/login`.
|
||||
7. Sign in again with the same admin credentials. The data on the
|
||||
7. If the server process is terminated during the database/uploads swap,
|
||||
restart the server. Before accepting requests, startup recovery uses the
|
||||
durable restore manifest to restore the complete old generation or finalize
|
||||
the complete verified new generation; it never intentionally boots with a
|
||||
mixed database/uploads generation. An ambiguous incomplete generation fails
|
||||
startup closed and preserves the manifest and artifacts for diagnosis.
|
||||
8. Sign in again with the same admin credentials. The data on the
|
||||
target environment now matches the source backup.
|
||||
|
||||
## Manual reset happy path
|
||||
|
||||
Reference in New Issue
Block a user