mirror of
https://github.com/hanzoai/forge.git
synced 2026-10-30 15:00:39 +00:00
Audited against the live site, not just the source. git.hanzo.ai renders a clean DOM already, so what was left was the surface that source greps miss and live headers show. The one leak visibly served on every request: set-cookie: gitea_incredible= The remember-me cookie default was never rebranded. Renamed to hanzo_git_remember; existing remember-me sessions are invalidated once. The container was branding the site title upstream. Both entrypoints wrote APP_NAME="Gitea: Git with a cup of tea" into app.ini, overriding the already-correct Go default. Removed the shell default entirely so the value lives in exactly one place, setting.AppName; ini MustString fills an empty key with the default. Half-finished earlier passes, now finished: the iframe query params were already hanzo-*, but the postMessage payload keys and the window global were not; the settings page told users to sign with "-n gitea" while the verifier is the only thing that has to agree with it, so the namespace is now one exported constant rendered into the command. Also: local storage prefix, the fetch-action request header (made vendor-free per our header convention, both ends are ours), install-form database prefill, and the shipped example config, which additionally documented $GITEA_WORK_DIR and $GITEA_CUSTOM -- env vars this fork renamed to GIT_* long ago -- and a COOKIE_USERNAME key the code no longer reads. Deleted docker/manifest*.tmpl: dead Drone-era templates publishing to gitea/gitea on Docker Hub, referenced by nothing. Our docker dry-run was also pulling build cache from ghcr.io/go-gitea/gitea. Deliberately left, with reasons: - "The Gitea Authors" copyright headers (2938) and upstream PR/issue links (278). Attribution and provenance; removing them would be wrong. - /data/gitea on-disk layout. Renaming it is a data migration that orphans every existing install's db, sessions, avatars and attachments. - The "gitea" webhook type and migration source. Wire and DB values, and the migration source correctly names a third party we import from, the same way github and gitlab do. Display name already reads Hanzo Git. - X-Gitea-OTP, X-Gitea-Object-Type and the X-Gitea-* webhook delivery headers. External client contracts on a live host; renaming them belongs in its own change, not a branding sweep. - gitea-azuread__a and sodipodi:docname in web_src/svg. Verified these never reach the DOM: svgo cleanupIds rewrites the ids and removeEditorsNSData strips the editor metadata before the asset is written. Co-authored-by: Hanzo Dev <[email protected]>
325 B
325 B
Hanzo Git - Docker
Dockerfile is found in the root of the repository.
The image is published as ghcr.io/hanzoai/git, built on our own runners. Never build the image locally.
Documentation on using the docker image can be found on the Hanzo docs site.