chore: update DETAILED_GAPS_AND_ISSUES_LIST and apply-token-aggregation-fix.sh
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- Refined instructions for applying the nginx fix and deploying configurations on VMID 5000. - Enhanced the script to handle the absence of the postgres user more gracefully, allowing for migrations to be run in different contexts. Made-with: Cursor
This commit is contained in:
@@ -81,6 +81,19 @@ Single contract retry: `./scripts/verify/run-contract-verification-with-proxy.sh
|
||||
|
||||
---
|
||||
|
||||
## 5a. LAN: Token-aggregation DB and migrations (VMID 5000)
|
||||
|
||||
If `/health` returns "database token_aggregation does not exist":
|
||||
|
||||
```bash
|
||||
./scripts/apply-token-aggregation-fix.sh # create DB, run migrations, restart (via Proxmox)
|
||||
./scripts/apply-token-aggregation-fix.sh --dry-run # print steps only
|
||||
```
|
||||
|
||||
If VMID 5000 has no `postgres` user, run `createdb` and migrations on the host where PostgreSQL runs, or set token-aggregation `DATABASE_URL` to `explorer_db` and run `smom-dbis-138/services/token-aggregation/scripts/run-migrations.sh` there.
|
||||
|
||||
---
|
||||
|
||||
## 5b. LAN: Chain 138 next steps (Phase 2: preflight → mirror+pool → register c* as GRU → verify)
|
||||
|
||||
**Ref:** [DEPLOYMENT_ORDER_OF_OPERATIONS](../03-deployment/DEPLOYMENT_ORDER_OF_OPERATIONS.md) Phase 2. Use when mirror/pool/GRU registration or verify are pending.
|
||||
|
||||
Reference in New Issue
Block a user