A self-hosted Forgejo or Gitea instance is really two systems bolted together: a web application backed by Postgres, and a collection of bare git repositories on the filesystem. Anything that needs to show git data in the web UI has to shell out to the binary and parse text, which is why something as straightforward as a blame view requires spawning a subprocess rather than running a query. If the git data lived in the same Postgres instance as everything else, that boundary disappears.
docker compose up -d
，详情可参考Line官方版本下载
└───────────────────────┘
4 A good discussion on luminance and how to calculate it can be found on this stack exchange question. ↑