Restore the repository before cutting over

PostgreSQL physical backups cover its databases. They do not contain Forgejo's separate Git, LFS and attachment files. A complete recovery also needs consistent database and file snapshots, encrypted recovery configuration, and a tested restore procedure. Retained volumes alone are not backups.

For Git history, prepare a stable local mirror and verify a portable bundle:

git clone --mirror https://forge.example.test/example-firm/sample-litigation.git /path/to/mirror.git
navigator ops forgejo bundle /path/to/mirror.git /path/to/repository.bundle

The command restores into a scratch mirror and checks object integrity, ref hashes and the default branch before publishing a new file without overwrite. It covers refs present in that mirror, including explicitly fetched PR refs. It excludes forge metadata, LFS and document objects. It does not schedule or upload archives.