zeekayandHanzo AI
0412e26125
CI/CD / render (push) Waiting to run
zoo.vote and zoo.industries are static bundles a pod was re-serving on every request. Both move to the site plane: the `public/` tree of the image digest each Deployment ran is synced to s3://hanzo-sites/zoo/vote and s3://hanzo-sites/zoo/industries, and each file now declares the Middleware that reads the prefix together with the route that names it. zoo-industries' server generated /public/config.json at boot from three SPA_* variables; the plane has no boot, so that file travels in the prefix carrying the values the pod served. zoo-ngo is deleted rather than converted. zoo.ngo and www.zoo.ngo already route to s3://hanzo-sites/zoo/ngo, and that prefix holds a newer build than the pod was serving to nobody -- no route in this namespace named it. A site declared twice is a site that goes stale in one of them. Co-authored-by: Hanzo AI <[email protected]>
Zoo Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/zoo/universe
This tip is an ancestor of canonical main, so no commit reachable from this
branch is unique to it — the canonical repo is a strict superset. Nothing was
lost by stopping here.
Two universes for one org is a split brain: a push lands somewhere real, reports
success, and never reaches a cluster, because CD reconciles the other one
(deploy/applicationset.yaml names the canonical URL). One repo per org means
that failure cannot happen.