This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Runbook — Forgejo Recovery

This runbook complements Forgejo’s version-specific administrative backup/restore procedure. Test against the deployed version before an incident.

Required backup set

• Forgejo database and configuration.
• Repository storage, including the separate PrivateServer-RS.wiki.git repository.
• Git LFS, attachments, releases, packages, avatars, and action data where used.
• Secret/encryption material required to read the backup, stored separately.
• Repository/permission inventory and checksum manifest.

Restore drill

1. Provision an isolated Forgejo instance matching the backed-up version and storage/database expectations.
2. Restore configuration and secrets with access limited to the recovery operator.
3. Restore database and repository/LFS/attachment storage as a consistent set.
4. Start without public ingress; inspect migration and integrity logs.
5. Verify the main repository, wiki pages/sidebar/footer, issues #1–#13, milestones, labels, mirror state, attachments/LFS, and permissions.
6. Clone the main and wiki repositories, run git fsck --full, and validate the machine-readable catalog.
7. Run one selected baseline restore/smoke test.
8. Record recovery time, deviations, missing data, and corrective issues before destroying the drill environment.

The scheduled wiki bundle workflow is a convenient checkpoint on the same Forgejo infrastructure. It is not the independent copy required by the 3-2-1 policy.