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.
"But what kind of implications will they have for energy and the environment?"
。关于这个话题，WPS下载最新地址提供了深入分析
他背对着我们，说：“好，好，我过去坐坐。”
– character identity
21 hours agoShareSave