2026-02-10 11:32:49 -08:00
# Deployment Documentation
2026-04-07 23:22:12 -07:00
Deployment docs for the Chain 138 explorer stack.
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
## Read This First
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
For the current production deployment shape, start with [`LIVE_DEPLOYMENT_MAP.md` ](./LIVE_DEPLOYMENT_MAP.md ).
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
That file reflects the live split deployment now in production:
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
- Next frontend on `127.0.0.1:3000` via `solacescanscout-frontend.service`
- explorer config/API on `127.0.0.1:8081` via `explorer-config-api.service`
- Blockscout on `127.0.0.1:4000`
- token aggregation on `127.0.0.1:3001`
- static config assets under `/var/www/html/config`
- CCIP relay workers on host `r630-01` , outside VMID `5000`
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
## Current Canonical Deployment Paths
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
- Frontend deploy: [`scripts/deploy-next-frontend-to-vmid5000.sh` ](../scripts/deploy-next-frontend-to-vmid5000.sh )
- Config deploy: [`scripts/deploy-explorer-config-to-vmid5000.sh` ](../scripts/deploy-explorer-config-to-vmid5000.sh )
- Explorer config/API deploy: [`scripts/deploy-explorer-ai-to-vmid5000.sh` ](../scripts/deploy-explorer-ai-to-vmid5000.sh )
2026-04-10 12:52:17 -07:00
- RPC/API-key edge enforcement: [`ACCESS_EDGE_ENFORCEMENT_RUNBOOK.md` ](./ACCESS_EDGE_ENFORCEMENT_RUNBOOK.md )
2026-04-07 23:22:12 -07:00
- Public health audit: [`scripts/check-explorer-health.sh` ](../scripts/check-explorer-health.sh )
- Full public smoke: [`check-explorer-e2e.sh` ](../../scripts/verify/check-explorer-e2e.sh )
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
## Legacy And Greenfield Docs
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
The rest of this directory is still useful, but it should be treated as legacy scaffold or greenfield reference unless it explicitly matches the live split architecture above.
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
- `DEPLOYMENT_GUIDE.md` : older full-stack walkthrough
- `DEPLOYMENT_TASKS.md` : older monolithic deployment checklist
- `DEPLOYMENT_CHECKLIST.md` : older tracking checklist
- `QUICK_DEPLOY.md` : command reference for the legacy package
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
## Practical Rule
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
If the question is "how do we update production today?", use:
2026-02-10 11:32:49 -08:00
2026-04-07 23:22:12 -07:00
1. [`LIVE_DEPLOYMENT_MAP.md` ](./LIVE_DEPLOYMENT_MAP.md )
2. the specific deploy script for the component being changed
3. the public health scripts for verification