mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-20 15:07:40 +00:00
zeekayandHanzo Dev
15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
Most of it was stale, not cosmetic: the docs taught `TRAEFIK_*` env, `traefik.http.*` labels, `traefik.ingress.kubernetes.io/` annotations, `.traefik.yml` plugins and `traefik_*` metrics. This binary answers to `INGRESS_*`, `ingress.http.*`, `ingress.kubernetes.io/`, `.ingress.yml` and `ingress.*` — a reader following the old text configured nothing. Two were worse than stale. Gateway API examples gave `group: traefik.io` for an IngressService backendRef, which kubernetes.go:1265 refuses against hanzo.ai. The contributing guide built with `github.com/traefik/ingress` ldflags against a module that is `github.com/hanzoai/ingress/v3`. script/code-gen.sh globs `hanzo.ai_*.yaml` and matched nothing — the per-CRD dumps had been deleted and never regenerated, so `cat` failed the script under `set -e`. controller-gen v0.19.0 restores all ten; they concatenate byte-for-byte into the committed definition and fixture. CHANGELOG.md is untouched: 6,789 lines of imported release history, where a rewrite would falsify the record rather than rebrand it. `@traefiklabs/faency`, `traefik/whoami`, k3s's `--disable=traefik`, the `traefik.io` CRD group and the MIT attribution stay — upstream's addresses, not our brand. Co-authored-by: Hanzo Dev <[email protected]>
Hanzo Ingress Web UI
Access to Hanzo Ingress Web UI, ex: http://localhost:8080
Interface
Hanzo Ingress Web UI provides 2 types of information:
- Providers with their backends and frontends information.
- Health of the web server.
How to build (for backend developer)
Use the Makefile :
make build-image # Generate Docker image.
make clean-webui generate-webui # Generate static contents in `webui/static/` folder.
How to build (only for frontend developer)
-
Go to the
webui/directory -
To install dependencies:
pnpm install
-
Build static Web UI:
pnpm build
-
Static contents are built in the
webui/static/directory
Do not manually change the files in the webui/static/ directory
The build allows to:
- optimize all JavaScript
- optimize all CSS
- add vendor prefixes to CSS (cross-browser support)
- add a hash in the file names to prevent browser cache problems
- optimize all images at build time
- bundle JavaScript in one file
How to edit (only for frontend developer)
Do not manually change the files in the webui/static/ directory
- Go to the
webui/directory - Edit files in
webui/src/ - Create and populate the
.envfile using the values inside.env.samplefile. - Run in development mode :
pnpm dev
- The application will be available at
http://localhost:3000/. On development mode, the application will run with mocked data served by Mock Service Worker.
How to run tests
- Execute the following commands:
pnpm test- or
pnpm test:watchif you want them in watch mode