zeekayandHanzo Dev
3fea396568
The zoo/hanzo/pars brand deployments had been crashlooping at 0 ready since June: their brand images bake NETWORK_NAME/currency/colors, but the runtime envs-validator requires NETWORK_NAME in the rendered env and the brand configmaps never set it — so every pod restart died on "NEXT_PUBLIC_NETWORK_NAME is a required field". The lux configmap already carries SKIP_ENVS_VALIDATION for the identical OIDC-placeholder reason; add it to the three brand configmaps (mainnet + testnet) so they boot on their baked brand identity. Restores the three brand explorers and lets the just-corrected chainId (pars 494949) + /v1 RPC configmap values take effect. Co-authored-by: Hanzo Dev <[email protected]>
DEPRECATED — see ~/work/lux/explorer/
The standalone Next.js frontend in this repo is no longer deployed. Its build output is embedded directly into the Lux Explorer Go binary (
ghcr.io/luxfi/explorer:1.2.1) viago:embed. Run that single binary in production.This repo is preserved as the source of the embedded SPA assets. Updates to the UI ship via a rebuild of the explorer image, not by deploying this Next.js app separately.
Canonical deploy:
~/work/lux/explorer/(Go binary, single process, indexer + GraphQL + SPA, port 8090).
Lux Explore frontend (legacy)
Frontend application for Lux Network blockchain explorer
Running and configuring the app
App is distributed as a docker image. Here you can find information about the package and its recent releases.
You can configure your app by passing necessary environment variables when starting the container. See full list of ENVs and their description here.
docker run -p 3000:3000 --env-file <path-to-your-env-file> ghcr.io/blockscout/frontend:latest
Alternatively, you can build your own docker image and run your app from that. Please follow this guide.
For more information on migrating from the previous frontend, please see the frontend migration docs.
Contributing
See our Contribution guide for pull request protocol. We expect contributors to follow our code of conduct when submitting code or comments.
Resources
- App ENVs list
- Contribution guide
- Making a custom build
- Frontend migration guide
- Manual deployment guide with backend and microservices
License
This project is licensed under the GNU General Public License v3.0. See the LICENSE file for details.