zeekayandHanzo Dev
a0b748828a
Audited what users and operators actually see, not raw grep counts. The rendered DOM, page titles, meta and footer on git.hanzo.ai were already clean; the frontend bundle is clean on main (the live hits were a stale deployed image, v1.26.19). What survived was server-side text and locales. User-visible: - Locale values: 12 -> 0 across 11 languages. The bulk was the admin self-check telling operators to run "gitea doctor convert"; our binary is gitd, so the instruction was wrong as well as off-brand. - Credential prompt realm when OAuth2 is disabled (the branch whose job is to NOT match Git Credential Manager's "Gitea" probe). - Admin diagnosis download is hanzo-git-diagnosis-*.zip; dump artifacts are hanzo-git-dump-*.zip / hanzo-git-db.sql. - Azure AD icon gradient ids no longer carry the upstream name. Source hygiene only: svgo cleanupIds already rewrote them before shipping. Outbound identity (what third parties see): - User-Agent to OAuth providers, haveibeenpwned and remote LFS servers is now Hanzo Git. The git-lfs "git-lfs/<version>" prefix is untouched; some LFS servers parse it. Operator-visible: - CLI help, descriptions and examples name gitd, not gitea. Several were telling operators to run commands that do not exist. - Migration/startup failure text (wrong-DB-version, no-SQLite-support, collation warning, internal-API contact error). The "upgrade to Gitea 1.6.4 first" note keeps the upstream name: that release is a real point in the schema lineage and renaming it would make it a lie. - Prometheus namespace gitea_ -> hanzogit_. Verified metrics are disabled on git.hanzo.ai, so no dashboard exists to break; this is the cheapest moment to do it. - Default log file, PID file, and the container entrypoint message. - Our own X-* headers are now function-namespaced per the platform's vendor-free convention: X-Cache-Debug, X-Internal-Auth, X-LFS-Content-Length, X-Vite-Dev-Server. Every side ships in one binary, so the rename is atomic. Correctness found on the way: - LLM.md documented GITEA__<section>__<KEY>; only GIT__ is accepted and there is no fallback, so a stale GITEA__ var is silently ignored. - EnvConfigKeyPrefixGitea held "GIT__" — name now matches its value. - api_packages_container_test.go still asserted the old registry realm while the code emits ours, so that test could not pass. - README told developers to run ./gitea web; docs/build-setup.md told contributors to clone go-gitea/gitea instead of this fork. Deliberately kept, and why, recorded in LLM.md: MIT attribution, dependency import paths, addressing values whose rename silently redirects (webhook type, .gitea/ repo conventions, index and analyzer names, /data/gitea), the GCM interop realm, and three wire contracts with external consumers (X-GITEA-OTP, webhook delivery headers, mail headers) that need an owner decision rather than a blind rename. Co-authored-by: Hanzo Dev <[email protected]>
1.3 KiB
Hanzo Git
Hanzo's self-hosted Git forge — Git hosting, code review, issues, packages, and CI/CD (GitHub-Actions-compatible), IAM-native via hanzo.id OIDC. Runs at git.hanzo.ai.
A white-label fork of Gitea (MIT). Upstream copyright and licensing are preserved in LICENSE; identity is wired to Hanzo IAM rather than local accounts, and the product is branded Hanzo Git.
Build & deploy
One way, like every Hanzo repo: the root hanzo.yml declares the
image and tests; a ~7-line .hanzo/workflows/cicd.yml
imports hanzoai/ci, which builds and pushes
ghcr.io/hanzoai/git on our own runners against git.hanzo.ai. Never build the image locally.
The running service is defined in hanzoai/universe (the git operator App CR):
a single-writer SQLite deployment, config injected via the GIT__<section>__<KEY>
env contract, OIDC login reconciled to hanzo.id.
Development
See docs/development.md for a local environment.
After building, run ./gitd web to start the server, or ./gitd help for
all commands.