deploy-vps-local-ag

Deploy OmniRoute to a local VPS via 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-ag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-vps-local-ag
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/deploy-vps-local-ag
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill deploy-vps-local-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of repeatedly deploying and updating OmniRoute on a self-hosted local server without manual, error-prone steps.

Core Features & Use Cases

  • Local build and packaging: Builds the latest OmniRoute CLI and creates a versioned npm package tarball for transfer.
  • Secure transfer to a LAN VPS: Copies the packaged tarball to the Local VPS via SCP.
  • Managed runtime deployment: Installs the package globally, rebuilds required native dependencies, and restarts OmniRoute using PM2.

Use case: You want to push frequent OmniRoute updates to a fixed internal server (192.168.0.15) and keep the service running reliably on port 20128.

Quick Start

Run the deploy flow to build, pack, scp the tarball to 192.168.0.15, restart the PM2 process, and verify the service by checking the HTTP response from http://192.168.0.15:20128/.

Frequently Asked Questions about deploy-vps-local-ag

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

FAQPage Schema
How do I deploy a Node.js application to a local VPS using SCP and PM2?

To deploy a Node.js application to a local VPS, package the build artifact using npm pack, transfer the tarball to the server via SCP, install it globally, rebuild native dependencies, and restart the managed process using PM2.

What is the best way to automate self-hosted OmniRoute updates over a LAN?

Automating self-hosted OmniRoute updates over a LAN requires packaging the CLI locally, securely copying the tarball to the internal server via SCP, and executing remote SSH commands to install the package and restart the PM2 process deterministically.

Can I use PM2 to restart a Node.js service automatically after transferring a new build via SCP?

Yes, after transferring the new build artifact via SCP, you can use SSH to run remote commands that install the package globally and execute a PM2 restart to reload the Node.js service with zero manual intervention.

Do I need npm pack to create a versioned tarball before deploying to a local VPS?

Yes, running npm pack is required to create a versioned package tarball, which serves as the deterministic build artifact transferred via SCP and installed globally on the target VPS.

Why does my Node.js deployment fail after SCP transfer when rebuilding native dependencies?

Node.js deployments can fail after SCP transfer if native dependencies are not rebuilt on the target server, which is why the deployment workflow includes a remote installation step to globally install the package and rebuild required native modules before restarting PM2.