omniroute-maintain
Use when updating/fixing OmniRoute. Production-only behind /omniroute; webpack build; never npm run dev.
- License 许可
- MIT
- 最近更新
- 2026-09-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- omniroute-maintain
- description
- Use when updating/fixing OmniRoute. Production-only behind /omniroute; webpack build; never npm run dev.
02 资源文件 8
- 脚本hermes-plugin-omni/__init__.py5.6 KB
- 参考文档hermes-plugin-omni/plugin.yaml146 B
- 参考文档references/9router-migration.md11.2 KB
- 参考文档references/reverse-proxy-rule.md2.5 KB
- 参考文档references/supervisor.conf1000 B
- 脚本scripts/update-via-proxy.sh13.1 KB
- 脚本scripts/verify-login.mjs1.5 KB
- 脚本scripts/verify.sh6.2 KB
03 SKILL.md 正文
OmniRoute Maintenance (reverse-proxy deployment)
Current Deployment (verified 2026-08-30 — production)
| Key | Value |
|---|---|
| Source | /home/workspace/Projects/omniroute/ |
| Git | release/v3.8.51 (upstream release-branch tip) |
| Supervisor | omniroute in /etc/zo/supervisord-user.conf |
| Start command | run-standalone.mjs from .build/next/standalone (applies OMNIROUTE_MEMORY_MB=4096) |
| Port | 20128 |
| BASE_PATH | /omniroute (pinned in .env + supervisor + Zo env) |
| Public base (OAuth) | NEXT_PUBLIC_BASE_URL=https://zo-reverse-proxy-sillyhippy.zocomputer.io/omniroute |
| Session cookies | AUTH_COOKIE_SECURE=true |
| Public API | https://zo-reverse-proxy-sillyhippy.zocomputer.io/omniroute/v1 |
| OAuth redirect | https://zo-reverse-proxy-sillyhippy.zocomputer.io/omniroute/callback |
| Zo service | svc_ZSZehS2z81g — mode=process, public=false |
| Browser URL | https://zo-reverse-proxy-sillyhippy.zocomputer.io/omniroute/ |
| Hermes / API | http://127.0.0.1:20128/omniroute/v1 (NEVER the proxy host) |
| Proxy route | { prefix: "/omniroute", target: "http://localhost:20128", preservePrefix: true } |
| Data DB | /root/.omniroute/storage.sqlite |
Canonical files (keep all three in sync after every edit):
/home/workspace/Skills/omniroute-maintain/(source of truth)/root/.hermes/skills/omniroute-maintain//root/.hermes/skills/devops/omniroute-maintain/
⛔ scripts/dev/run-standalone.mjs is PRODUCTION
The path contains dev. That is the upstream filename. It is not npm run dev.
It is the production wrapper: cwd = .build/next/standalone, NODE_ENV=production, applies OMNIROUTE_MEMORY_MB → --max-old-space-size, then starts server-ws.mjs (fallback server.js).
Forbidden start commands (all of these are wrong on this VPS):
npm run dev/next dev/ Turbopack HMR- bare
node .build/next/standalone/server.js(ignores the 4096 heap pin → empty model list / 503) npm start
Correct supervisor command (exact):
command=bash -c 'cd /home/workspace/Projects/omniroute/.build/next/standalone && exec node ../../../scripts/dev/run-standalone.mjs'
plus NODE_ENV="production" and OMNIROUTE_MEMORY_MB="4096".
Live check: tr '\0' '\n' < /proc/$(pgrep -f run-standalone.mjs | head -1)/environ | grep NODE_ENV must be production. Process title on :20128 is omniroute (v16…) — not next-server from another app.
Zo Computer’s own UI (next-server on :3088 under /__modal/volumes/.../web-standalone) is not OmniRoute. Do not kill it. Do not treat it as OmniRoute dev mode.
⛔ HARD RULE — never npm run dev behind the reverse proxy
npm run dev needs a WebSocket to /_next/webpack-hmr. zo-reverse-proxy does not proxy that → login stuck on "Loading...". curl 200 is a lie.
⛔ UPDATE RULES (2026-08-30 — yesterday’s break)
npm run build defaults to Turbopack. Turbopack native RAM hit 14GB+ here, never finished, and a killed/timed-out build wipes .build/next/standalone so OmniRoute cannot start.
- Only
bash /home/workspace/Skills/omniroute-maintain/scripts/update-via-proxy.sh. Do not invent a secondnpm run build. - Webpack only:
OMNIROUTE_USE_TURBOPACK=0. Never Turbopack on this VPS. - Build heap 10GB (
OMNIROUTE_BUILD_MEMORY_MB=10240). Runtime stays 4096. Abort if available RAM drops under 1500MB. - Never start a second build. If
build-next-isolated.mjs/next buildis already running, wait or stop — do not launch another. - Do not stop OmniRoute until the new standalone exists (
BUILD_ID+.build/next/standalone/server.js). Stopping first + a dead build = site down. - Do not
npm installunless the user asked (OMNIROUTE_NPM_INSTALL=1). Install is the RAM-heavy path. - Run the update detached (session disconnect must not SIGTERM the build). A killed build deletes standalone.
- Update backups (
/home/workspace/Backups/omniroute-update-*) are config + sqlite only. They do not contain a restorable standalone. The Aug 13 zip the watchdog named is gone and was config-only anyway. Failed build → re-run webpack, do not pretend a zip restore will bring:20128back. verify.shmust requirerun-standalone.mjs. Bareserver.js/npm startis a FAIL.
IDIOT-PROOF UPDATE (run this — do not invent steps)
/omni update
/omni verify
/omni status
Or:
bash /home/workspace/Skills/omniroute-maintain/scripts/update-via-proxy.sh
- Git upgrade to latest
release/vX.Y.Zis ON (OMNIROUTE_GIT_PULL=0to skip). OMNIROUTE_NPM_INSTALL=1— alsonpm install(off by default; do not turn on for RAM).
Then:
bash /home/workspace/Skills/omniroute-maintain/scripts/verify.sh
If verify fails: stop. Re-pin + webpack rebuild. Do not claim success.
What every model must remember
OMNIROUTE_BASE_PATHstays/omniroute.- Supervisor stays
run-standalone.mjs+OMNIROUTE_MEMORY_MB=4096+NODE_ENV=production. - Every update = webpack production build (
OMNIROUTE_USE_TURBOPACK=0) withOMNIROUTE_BASE_PATH=/omniroutebefore restart. - Proxy prefix stays
/omniroute+preservePrefix: true. - Hermes URL stays
http://127.0.0.1:20128/omniroute/v1. - Root
http://127.0.0.1:20128/v1is wrong (404). - Never point Hermes at
zo-reverse-proxy-.../omniroute/v1. - Zo
mode=process— do not passlocal_port. - After Zo MCP
update_user_service, re-pin supervisor env. - curl UI 200 is not enough —
verify-login.mjsmust see a password field. - Do not
git reset --hard/git checkout .to “clean” before updating.
Manual checklist (only if the script cannot run)
- Backup
.env,proxy.ts, supervisor conf,storage.sqlite. - Confirm pins (
.env,run-standalone.mjs+ production, Zo env, proxy.ts). - Leave OmniRoute running. If a build is already in flight, do not start another.
cd /home/workspace/Projects/omniroute && OMNIROUTE_BASE_PATH=/omniroute OMNIROUTE_USE_TURBOPACK=0 OMNIROUTE_BUILD_MEMORY_MB=10240 NODE_OPTIONS=--max-old-space-size=10240 npm run build- Confirm
.build/next/BUILD_IDand.build/next/standalone/server.jsexist. supervisorctl -s http://127.0.0.1:29011 restart omniroute- Wait until
curltohttp://127.0.0.1:20128/omniroute/v1/modelsis200or401. supervisorctl -s http://127.0.0.1:29011 restart zo-reverse-proxy- Run
scripts/verify.sh.
Do not restart the Hermes gateway unless the user says so. Catalog rediscovery is /restart on Telegram.
Hermes providers that hit OmniRoute
providers:
omniroute:
base_url: http://127.0.0.1:20128/omniroute/v1
key_env: OMNIROUTE_API_KEY
venice:
base_url: http://127.0.0.1:20128/omniroute/v1
key_env: OMNIROUTE_API_KEY
Rollback
See references/reverse-proxy-rule.md → Rollback.
Config backup example: /home/workspace/Backups/omniroute-update-20260830_152521/.
That restores .env / sqlite / proxy / supervisor — not the Next standalone.
Related
- DB / providers:
omniroute-management - Zo HTTP→process:
zo-service-registration references/reverse-proxy-rule.mdreferences/supervisor.conf—run-standalone.mjs+ productionscripts/verify.sh/scripts/verify-login.mjs/scripts/update-via-proxy.sh
04 同仓库更多 Skills
zopack
Export and import zo.space route setups as shareable .zopack.md files. Use when the user wants to package their zo.space routes for sharing, or when they receive a .zopack.md file to deploy. Triggers on "export my zo.space", "create a zopack", "import this zopack", or any mention of .zopack.md files.
zoho-mail-inbox
Full inbox management for Zoho Mail (info@justlegalsolutions.org) — list unread, mark all as read, delete by sender/keyword, search, send from aliases, list folders. Fully self-contained — zero setup needed.
weekly-meeting-reminder
Get an email every Sunday evening listing your meetings for the coming week.
Let Zo use your X (Twitter) account
zo-tools
Internal process tools for Zo and Hermes — local search, document processing, OCR, and embeddings. All services run on localhost, zero HTTP slots consumed.
ssh-setup
Sets up secure remote access to your Zo Computer so you can connect from anywhere