Lately we had been suffering several issues related to Gitea, those
being absurd resource hog and massive CPU usage that skyrocketed beyond
100%, leading to other services being dysfunctional, such as the Misskey
instance we run.

Mima had the decision to stop it until next notice, and I have talked
with him on the headquarters about migrating from Gitea to git-daemon
and cgit.

He didn't seem to mind at all, and the same day I began working on it,
setting up the daemon was not difficult, neither was moving the
repositories, et cetera.

Cgit was eventually installed and everything, but I had one major
problem, git clones over https:// plain stopped working, and the Go
toolchain only uses that instead of a (in my opinion) saner approach,
such that if https:// clones weren't available, and if it git:// was,
the latter would be used as fallback.

Most of my personal struggles were with fcgiwrap(8) throwing 403 to any
request going to git-http-backend(1), until I remembered I still had
slowcgi(8) installed and used that instead later on.

By that point at the next day I just went and installed stagit(1) from
the repositories and managed to work up some magic with nginx(8) to have
them indexed. 

Later today I actually bothered to look at <https://forgeperf.org>,
which is linked on <gopher://bitreich.org/1/forgeperf> and figured that
stagit was really that fast, and Evil_Bob concluded it wasn't listed
because of said fact. Et cetera

Now everything sort of works, and I don't have to care.

また後で