mirror of
https://github.com/hanzoai/forge.git
synced 2026-10-30 15:00:39 +00:00
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
1.2 KiB
Hanzo Forge
Hanzo 自架的 Git 平台 — Git 託管、程式碼審查、問題追蹤、套件庫，以及相容於 GitHub Actions 的 CI/CD，並透過 hanzo.id OIDC 原生整合 IAM。服務位於 git.hanzo.ai。
本專案採用 MIT 授權。上游版權與授權記錄於 NOTICE 與 LICENSE；身分驗證改接 Hanzo IAM 而非本機帳號。
建置與部署
如同每個 Hanzo 儲存庫，只有一種方式：根目錄的 hanzo.yml 宣告映像檔與測試；
約七行的 .hanzo/workflows/cicd.yml 匯入 hanzoai/ci，於我們自己的 runner 上建置並推送
ghcr.io/hanzoai/git。切勿在本機建置映像檔。
執行中的服務定義於 hanzoai/universe（git operator App CR）：單寫入者 SQLite
部署，組態經由 GIT__<section>__<KEY> 環境變數契約注入，OIDC 登入對接 hanzo.id。
開發
本機環境請見 docs/development.md。建置完成後，執行
./gitd web 啟動伺服器，或 ./gitd help 檢視所有指令。