17c4ddcd850127031aba127ff38a5e8248d17cce
Both were scraped off do-sfo3-zoo-k8s, the DigitalOcean cluster that no longer exists. zoo-zips runs the only nginx left in the fleet and answers 669 bytes of meta-refresh, while the real zips.zoo.ngo serves 96 KB from elsewhere. work-board duplicates the one behind work.hanzo.network; work.zoo.network does not resolve. Co-authored-by: Hanzo Dev <[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.
Description
Declared state for the zoo fleet: one values file per service, one ApplicationSet
1.2 MiB
Languages
TypeScript
70.1%
Shell
21.5%
Makefile
8.4%