zeekay
2ff64fe352
explore.lux.network measured nothing. It carried a Google Analytics component that no deployment had ever given a property id, so every visit to the explorer went unrecorded and there was no way to tell whether a change to the site helped anyone. This is one of seven Lux surfaces moving onto first-party analytics. Pageviews now go to Hanzo Insights through @hanzo/event, the client the rest of the fleet already reports with. It mounts once in _app, in the slot the Google tag used to occupy, so every route is covered: the provider records the first view and the route tracker records each one after it. The ingest key is publishable and write-only, so it belongs in the bundle, and a deploy can point the surface at another project with NEXT_PUBLIC_PUBLISHABLE_KEY. The new CSP entry allows api.hanzo.ai so the beacon survives wherever that policy is enforced. Google Analytics is removed rather than left running alongside, together with its feature config, CSP entry and environment variable, because two stacks measuring the same site is how you end up trusting neither. Error reporting stays with Rollbar, which this app already runs.
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.