Thin deploy shim over luxfi/explore
that ships the Zoo Network blockchain explorer at explore.zoo.network
(and explore.zoo.ngo).
All application code lives in luxfi/explore. This repo contains only
deploy configuration — Dockerfile, compose, Kubernetes manifests, and
the Zoo-specific environment variables. When luxfi/explore detects a
Zoo hostname it automatically switches logo, favicon, brand colours, and
per-chain links via the multi-tenant chain registry
(configs/app/chainRegistry.ts).
Before this shim the repository was a ~2 GB fork of Blockscout/Lux
Explorer that drifted independently from upstream. Every security fix
and UI improvement in luxfi/explore had to be manually backported,
and that rarely happened. The shim inverts the dependency: upstream
owns the code, Zoo owns the deploy.
Dockerfile # FROM ghcr.io/luxfi/explore:latest, no local build
compose.yml # local dev against a Zoo node
k8s/ # production manifests for explore.zoo.network
env/zoo.env # NEXT_PUBLIC_* overrides (hostname, brand, RPC)
docker compose up # local dev
kubectl apply -k k8s/ # production (GKE zoo-k8s)The runtime image is always pulled by tag; no build step is required.
If Zoo needs changes to the application, open a PR against
luxfi/explore. The chain registry already supports per-chain branding,
per-chain routing, and per-chain network selectors without forking the
codebase.