zeekayandHanzo AI
8ed9b670fb
CI/CD / render (push) Failing after 0s
It pulled ghcr.io/parsdao/explore, an image whose repository does not resolve, and sat in ImagePullBackOff while the other four chains ran the same luxfi/explore image branded by their own configmap. A second image for a frontend that is already configured per chain is a second thing to keep current, and this one was never current. Co-authored-by: Hanzo AI <[email protected]>
Lux Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/lux/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.