deploy-vps-local-cc

Deploy OmniRoute releases to a local VPS via npm, scp, and PM2.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill deploy-vps-local-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-vps-local-cc
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/deploy-vps-local-cc
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill deploy-vps-local-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of getting the latest OmniRoute build running on a specific VPS reliably, without manual packaging and repetitive setup work.

Core Features & Use Cases

  • Build and package locally: Produces a clean npm tarball of the latest OmniRoute CLI build.
  • Transfer and install remotely: Uploads the tgz to the Local VPS and installs it globally while ignoring install scripts.
  • Restart and verify: Rebuilds the better-sqlite3 native dependency, restarts the PM2 process, and confirms the service responds on the expected port (20128).
  • Use Case: When OmniRoute is updated, quickly deploy the newest version to your Local VPS at 192.168.0.15 and ensure the endpoint is reachable.

Quick Start

Run the deployment flow to build a fresh OmniRoute package locally, scp it to 192.168.0.15, restart the PM2 service named omniroute, and verify it serves HTTP on port 20128.

Frequently Asked Questions about deploy-vps-local-cc

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

FAQPage Schema
How do I deploy OmniRoute to a local VPS using npm and PM2?

To deploy OmniRoute to a local VPS, build a clean npm tarball locally, secure copy it to the server, install it globally with ignore-scripts, rebuild better-sqlite3, restart the PM2 process, and verify HTTP availability on port 20128.

What is the best way to update an OmniRoute service on a fixed port remotely?

Updating an OmniRoute service remotely involves running a local npm pack with cache and log cleanup, transferring the tgz file via scp to /tmp, and executing a remote global installation followed by a PM2 restart and HTTP verification.

Does OmniRoute deployment with PM2 require rebuilding native dependencies like better-sqlite3?

Yes, OmniRoute deployment requires rebuilding the better-sqlite3 native dependency remotely after installation to ensure the database component works correctly within the PM2 process management environment on the target VPS.

How do I verify a remote OmniRoute deployment is running successfully after a PM2 restart?

You verify a remote OmniRoute deployment by making an HTTP verification call to the root path of the service, confirming it responds correctly on the expected fixed port 20128 after the PM2 restart and save process completes.

Why does npm pack and local build cleanup matter for VPS deployments?

Local build cleanup matters because it produces a clean npm tarball without cached files or logs, ensuring deterministic builds when transferring and installing the OmniRoute package remotely on the local VPS.

Can I install OmniRoute remotely without running npm install scripts on the VPS?

Yes, you can install OmniRoute remotely without running install scripts by using the ignore-scripts flag during the global npm installation step, which prevents unwanted script execution before rebuilding better-sqlite3 and restarting PM2.