zeekayandHanzo Dev
1615bba341
The brands are the same bytes — brand comes from the explore-env-<brand> ConfigMap the pod reads at runtime — so a release is one build and N registry copies. That copy step was a person, and the evidence a person is not a mechanism is that v1.1.25 and v1.1.26 were never copied: hanzo, pars and zoo sat on v1.1.22, four releases behind, with no image in their registries to advance a pin to even if someone had edited one. crane copy, not buildx imagetools create: the former preserves the manifest digest, the latter republishes it and can produce a new digest for identical content. Each copy is then asserted equal to the source digest per org — a green copy command is not an artifact, and a brand running bytes other than the ones that passed the test gate is the failure this exists to prevent. The image org now follows github.repository_owner, so a brand that forks this repo and fast-forwards to an upstream tag publishes to its own org and nowhere else. Only upstream fans out; a fork must not publish for other brands. 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.