deploy-vps-local-cx

Deploying OmniRoute to a VPS via PM2 involves building the package locally, creating an npm pack tarball, secure copying it to the server, installing globally with --ignore-scripts, rebuilding better-sqlite3, and restarting PM2 to update the endpoint.

Updating an on-prem OmniRoute endpoint reproducibly requires packaging a clean local build into an npm tarball, uploading it via scp to the VPS, and running a global npm install with --ignore-scripts before restarting the PM2 process.

Server verification after an SSH VPS deployment confirms the service is running by checking the HTTP endpoint response code, validating that the OmniRoute gateway is live and accessible at the specified local IP address and port.

Yes, you need to rebuild better-sqlite3 when deploying OmniRoute to a Local VPS because the global installation uses the --ignore-scripts flag, which skips native dependency compilation, requiring a manual rebuild step before restarting PM2.

Yes, you can use npm pack to create a deployment artifact for SSH transfer by running a local CLI build to produce a clean OmniRoute release tarball, which is then securely copied to the remote VPS /tmp directory for installation.

Deploying to a fixed Local VPS address limits the process to a specific on-prem host at 192.168.0.15, meaning the deployment workflow is not directly portable to dynamic hosts or cloud environments without modifying the target IP and verification endpoint.