deploy-vps-both-cc

Deploying a Node.js application to multiple VPS environments simultaneously requires building and packaging the artifact once, using SCP to transfer it to both hosts, and restarting the process with PM2. This ensures a consistent production rollout across servers.

The best way to restart a PM2 ecosystem process after SCP deployment is to install the package globally, rebuild native dependencies like better-sqlite3, and use the PM2 ecosystem config to apply environment updates and restart the running process.

npm pack works for consistent deployment artifacts by bundling the application locally into a single tarball. You then transfer this exact artifact via SCP to remote servers, guaranteeing both targets run the identical build without environment-specific inconsistencies.

Yes, you can deploy to both a cloud Akamai VPS and a local LAN VPS using the same workflow. The process builds once locally, transfers the package to both IP targets, and performs global npm installs with PM2 restarts on each host.

To verify a VPS deployment and run a health check after a production rollout, send an HTTP request to the configured port on each server. The process confirms successful deployment by checking that both endpoints respond with expected HTTP status codes.

You need to rebuild better-sqlite3 when restarting an application with PM2 because it is a native dependency. Rebuilding ensures the compiled binary matches the specific operating system and architecture of the target VPS during the global npm install step.