The Grafana mixin queried gitea_* while modules/metrics/collector.go emits
hanzogit_*, so every stat panel rendered empty with no error. All twelve
queried names now match names the collector registers.
Issue templates sent security reports to [email protected] and help requests
to upstream's Discord and forum, which SECURITY.md explicitly tells people not
to do; both now point at [email protected] and our docs, and the issue search
points at this repository. FUNDING.yml routed sponsorship to upstream's Open
Collective, so it is gone.
The VS Code build task wrote ./gitea. The Makefile, the README beside it and
.gitignore all say gitd.
Frontend: initGiteaFomantic, initGiteaAPIViewer and isGiteaError renamed for
what they do; the Fomantic hard-fork markers read FORGE-PATCH; base.css named
:gitea: as a CUSTOM_EMOJIS example, but the defaults are git, gitlab and github.
Container paths are deliberately untouched. /data/gitea is GIT_WORK_DIR's
default in docker/root/usr/local/bin/gitd, the deployment does not set
GIT_WORK_DIR, and SSH_SERVER_HOST_KEYS is a relative path -- moving the work
directory regenerates the host keys and every existing clone reports a changed
host identity. /var/lib/gitea, /etc/gitea, gitea.db and
gitea-trusted-user-ca-keys.pem keep their names because the matching defaults
live in modules/setting, and a path renamed on one side only is a server that
starts and then cannot find its own files.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
b8db2962cd
