Forgejo stores issues, pull requests, users, permissions, webhooks, branch protection rules, and CI status in Postgres already, and git repositories are the one thing left on the filesystem, forcing every deployment to coordinate backups between them, and the two systems scale and fail in different ways. The codebase already shows the strain: Forgejo mirrors branch metadata from git into its own database tables (models/git/branch.go) so it can query branches without shelling out to git every time.
5 August 2025ShareSave
，详情可参考纸飞机下载
Антонина Черташ
paper: “plain textured paper”
I've been battling support around the replacement, but was pleasantly surprised by the GrapheneOS backup experience. The upside from all of this is I needed to reinstall GrapheneOS and that gave me a chance to reflect on the last 8.4 months of using it.