zeekayandHanzo AI
e68b17ff9b
CI/CD / render (push) Failing after 0s
Each of these mounts a configmap named explore-env-<chain> that was declared nowhere: the deployments referenced it, nothing created it, and every frontend sat in CreateContainerConfigError. The same shape as the chain nodes, whose genesis and startup config never migrated either. The values are the RUNTIME set only. luxfi/explore's .env.example.lux mixes build-time and runtime variables in one file — NEXT_PUBLIC_BRAND is read by `pnpm build`, and the branding, marketplace and homepage URLs were dropped from the image — so feeding that file to a container fails the validator on congruity, then on deprecation, then on unknown names. 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.