zeekayandHanzo Dev
27cde39e36
Storage buckets, indexer names, the bleve analyzer, the lock prefix, SSH host keys, the markdown front-matter key, the container data paths, the RPM repo id and the API security scheme all read as this product now, and app.example.ini matches the code again. The upstream maintainer list and the changelog generator config went with the release history they belonged to, and the citation comments state the fact rather than link the issue. Three inert rules turn out to have been inert because they named a module path this tree does not use: gci grouped no first-party imports under prefix(), and depguard let models/migrations import models and modules/structs. They now name github.com/hanzoai/git. The config example also documented .gitea/workflows while the code has read .hanzo/workflows for some time. The authorized_keys marker follows the delegate-hook precedent: the new name is written and the old one is still recognised, because a marker we do not know is copied through as a hand-added key and leaves a revoked key authorized. The stored user_setting key keeps its value; only a migration may change that. Co-authored-by: Hanzo Dev <[email protected]>
1.2 KiB
Hanzo Forge
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.
MIT licensed. Upstream authorship and licensing are recorded in NOTICE and LICENSE. Identity is wired to Hanzo IAM rather than local accounts.
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.