Deployment
Docker and Kubernetes deployment guides
The Lux Explorer runs on Kubernetes with Docker containers. Five explorer instances serve different chains from the same binary, each with its own SQLite database and chain-specific branding.
Architecture
Traefik Ingress
explore.lux.network -> explorer-mainnet:4000
explore-zoo.lux.network -> explorer-zoo:4000
explore-hanzo.lux.network -> explorer-hanzo:4000
explore-spc.lux.network -> explorer-spc:4000
explore-pars.lux.network -> explorer-pars:4000Explorer Instances
| Instance | Domain | Chain | Backend RPC |
|---|---|---|---|
| C-Chain | explore.lux.network | Mainnet C-Chain | luxd-1:9630/ext/bc/C/rpc |
| Zoo | explore-zoo.lux.network | Zoo chain | luxd-1:9630/ext/bc/{id}/rpc |
| Hanzo | explore-hanzo.lux.network | Hanzo chain | luxd-1:9630/ext/bc/{id}/rpc |
| SPC | explore-spc.lux.network | SPC chain | luxd-1:9630/ext/bc/{id}/rpc |
| Pars | explore-pars.lux.network | Pars chain | luxd-1:9630/ext/bc/{id}/rpc |
Docker Images
| Component | Image |
|---|---|
| Explorer (Go) | ghcr.io/luxfi/explorer |
| Frontend (Next.js) | ghcr.io/luxfi/explore |
Kubernetes Requirements
- Container memory limit: 2Gi per instance (single Go binary, no PostgreSQL needed)
- Deployment strategy:
RollingUpdate - PVC for SQLite data persistence
- TLS via Traefik certResolver with letsencrypt