The backup tarred only /data/git, but CONTRACT_004 §4.2 requires the git repos AND app.ini AND the host SSH keys — without app.ini a restored Forgejo has no DB/S3 config and won't start. Discovered during the T13 DR rehearsal: restore reached Forgejo and it had nothing to configure from. Tar the whole /data volume (git/, gitea/conf/app.ini, ssh/ssh_host_*). It is ~1 MB at Layer 0 — the DB and LFS/packages are externalised to Postgres + RustFS, so /data holds no large recreatable state. Restored end-to-end on a fresh VM: Forgejo comes up fully configured against the restored PG + RustFS. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .gitkeep | ||
| backup-remote.sh | ||
| backup.sh | ||
| restore-remote.sh | ||
| restore.sh | ||