Module renamed to github.com/luxfi/explorer (was -unified). Imports
luxfi/indexer/{daemon,evm,storage,explorer} and luxfi/graph/{engine,
indexer,storage} as libraries; embeds the luxfi/explore SPA via go:embed
all:static.
A new ChainSupervisor wraps the existing ChainRegistry: adding a chain
(via config / mDNS / admin API) spawns a per-chain indexer goroutine plus
one graph engine + indexer per enabled subgraph; removing cancels them
and frees the routes from a sync.Map dispatcher mounted on /v1/indexer/,
/v1/explorer/ (legacy alias), and /v1/graph/.
Config schema is fully per-chain: indexer poll interval, list of graph
subgraphs (each can pick a built-in schema like amm, securities, fhe…),
brand (name/coin/accent + on-disk icon/logo paths), token features, and
top-level networks list. /envs.js exposes the chain list and active
brand to the SPA at runtime, so a deploy can rebrand by remounting
chains.yaml + assets — no image rebuild.
Dockerfile clones luxfi/explore + luxfi/indexer + luxfi/graph as
siblings inside the build, populates ./static from the SPA build, and
produces one binary. CI checks out the three repos as siblings so the
local replace in go.mod works without tagged releases.
4 repos, 4 images:
indexer → chain data (blocks, txs, tokens, contracts)
graph → subgraph events (swaps, pools, DeFi, GraphQL)
explore → Next.js frontend
explorer → all three combined (this)
Single image contains 3 binaries: indexer, graph, explorer.
Each can run standalone or together.
Three repos, three images:
luxfi/indexer → ghcr.io/luxfi/indexer (Go backend, API + indexing)
luxfi/explore → ghcr.io/luxfi/explore (Next.js frontend)
luxfi/explorer → ghcr.io/luxfi/explorer (this: combined single image)
Dockerfile pulls both repos at build time, embeds the Next.js static
export into the Go binary via go:embed, produces a single container.
zeekay