zeekayandHanzo Dev
6e013d6eb3
luxfi/explorer carries luxfi/graph and luxfi/indexer, and every network's
exchange-api already reads it at /v1/graph/{slug}/{amm,dex}/graphql. A second
Graph Protocol stack -- graph-node, its postgres, its ipfs -- served nothing.
Removes its declarations, its repo entry, and two stale exchange-api
declarations that still named it: lux-explorer runs no exchange-api at all,
and lux-ns runs from deploy/, so applying either would have pointed a live
service at a service that no longer exists.
Co-authored-by: Hanzo Dev <[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.