d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update DETAILED_GAPS_AND_ISSUES_LIST and apply-token-aggregation-fix.sh
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Details

Browse Source 
- 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:
defiQUG
2026-03-02 13:21:52 -08:00
parent 4fb2a27fbb
commit 6b540aff52
4 changed files with 32 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/04-configuration/DETAILED_GAPS_AND_ISSUES_LIST.md
View File

@@ -168,6 +168,6 @@
## 12. Remaining Operator Actions (Requires Proxmox/Server Access)
1. **Apply nginx fix and deploy config on VMID 5000:** Run `./scripts/apply-remaining-operator-fixes.sh` from repo root (LAN/operator). It runs `fix-nginx-conflicts-vmid5000.sh` inside VMID 5000 via `ssh root@<Proxmox> 'pct exec 5000 -- bash -s'`, then deploys explorer config via scp + pct push. **Applied 2026-03-02:** nginx fix and explorer config deploy completed successfully.
2. Create token_aggregation DB (or align explorer_db) and run migrations (see §2)
3. Restart token-aggregation after DB fix
1. **Apply nginx fix and deploy config on VMID 5000:** Run `./scripts/apply-remaining-operator-fixes.sh` from repo root (LAN/operator). **Applied 2026-03-02:** nginx fix and explorer config deploy completed successfully.
2. **Token-aggregation DB:** Run `./scripts/apply-token-aggregation-fix.sh` to create DB and run migrations inside VMID 5000. If the container has no `postgres` user, run `createdb`/migrations on the host where PostgreSQL runs, or point token-aggregation `DATABASE_URL` to `explorer_db` and run migrations there (see §2).
3. Restart token-aggregation after DB fix (script does this when postgres user exists).