omniroute-maintain

Updates and verifies an OmniRoute Next.js deployment running behind a reverse proxy.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/SillyHippy/zo-skills --skill omniroute-maintain-sillyhippy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omniroute-maintain
Source: https://github.com/SillyHippy/zo-skills/tree/main/skills/omniroute-maintain
Command: npx skills add https://github.com/SillyHippy/zo-skills --skill omniroute-maintain-sillyhippy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve? Updating a production OmniRoute instance behind a reverse proxy is fragile: Turbopack builds exhaust RAM, killed builds wipe the standalone output, and dev-mode HMR breaks login behind the proxy. This Skill encodes the exact safe update, verification, and rollback procedure so any agent can maintain the deployment without breaking it. ## Core Features & Use Cases - Idiot-proof update script: scripts/update-via-proxy.sh performs backup, git upgrade to the latest upstream release branch, re-pinning of BASE_PATH/supervisor/env config, webpack production build with RAM guards, and ordered restarts. - Deep verification: scripts/verify.sh plus a Playwright-based verify-login.mjs check supervisor state, basePath pins, proxy routes, local/public API health, and that the login page actually hydrates a password form. - Hermes slash commands: a plugin exposes /omni update, /omni verify, and /omni status for Telegram/CLI operation. - Use Case: After an upstream OmniRoute release, run /omni update to pull the release branch, rebuild with webpack (never Turbopack), restart services, and confirm the proxied UI and http://127.0.0.1:20128/omniroute/v1 API both work. ## Quick Start Ask the agent to update OmniRoute and verify the deployment, which runs the update-via-proxy script followed by the verification checks.

Frequently Asked Questions about omniroute-maintain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update OmniRoute running behind a reverse proxy?▼

Run the update-via-proxy.sh script or the /omni update slash command. It backs up config and the SQLite database, pulls the latest upstream release branch, re-pins OMNIROUTE_BASE_PATH, rebuilds with webpack, restarts services, and verifies the deployment.

Why is the OmniRoute login page stuck on Loading behind a proxy?▼

The app was started with npm run dev, whose HMR WebSocket is not proxied, so the page never hydrates. The deployment must run the production run-standalone.mjs wrapper with NODE_ENV=production; verify-login.mjs confirms a password field renders.

Should I use Turbopack or webpack to build Next.js on a RAM-limited VPS?▼

Use webpack. Turbopack's native build consumed over 14GB of RAM and never finished on this VPS, and a killed build wipes the standalone output. Set OMNIROUTE_USE_TURBOPACK=0 with a 10GB build heap.

How do I verify a Next.js app behind a reverse proxy is healthy?▼

Check supervisor status, basePath pins in .env and the routes-manifest, proxy route configuration, and local and public API responses. A curl 200 is insufficient, so a headless browser check confirms the login form actually hydrates.

What are the limitations of the OmniRoute update backups?▼

Update backups contain only configuration files and the SQLite database, not a restorable Next.js standalone build. If a build fails, you must re-run the webpack build rather than restoring from a backup zip.