Node.js process ops
PM2 is useful only when the deployment is documented.
A PM2-managed app should have a known process name, working directory, start command, environment source, startup behavior, log path, reload method, rollback note, and handover owner.
PM2Process supervisor
LogsRuntime evidence
StartupReboot safety
PM2 can make a Node.js app easier to run on a Linux VPS, but it can also hide operational details if nobody documents them. A process list alone is not a deployment strategy. The team should know how the app starts, which environment variables it needs, how it reloads, where logs live, and how it comes back after reboot.
Official source note: PM2 documents startup scripts for generating and configuring a process list that can resurrect applications after reboot: PM2 startup script documentation.
PM2 deployment path
01Define process, env, branch, build, and working directory02Save startup behavior, logs, reload, and rollback03Add monitoring and write handover notes
