PM2, or Process Manager 2 is an incredibly versatile production process manager written in Node.js.
PM2 has a lot of uses, let’s look at a few:
First thing we need to do is to install PM2 globally on your machine:
$ npm i -g pm2
Let’s get into the basics of how to use it. To start a process under PM2, all you have to do is run
pm2 start <app>. App being the name of the file you’re running. PM2 will output something like this:
[PM2] Starting C:\Users\moose\app.js in fork_mode (1 instance) [PM2] Done. ┌──────────┬────┬ │ App name │ id │ ├──────────┼────| │ app │ 0 │ └──────────┴────|
Reduced and simplified for brevity
Pay attention to what it says under
id. If you forget just run
pm2 list. If you want to add a name to the process when you start it, you can use the
--name parameter (
pm2 start app.js --name mycoolapp). Awesome! Your app is now running under PM2, if it crashes, PM2 will restart it.
Another awesome feature that PM2 has is restarting when a file in the working directory changes. To make PM2 watch our directory and restart on file changes, include the
--watch flag when you start your app.
PM2 also allows us to start our processes when our server (re)starts. Start whatever you want to have running all the time through
pm2 start and then run
$ pm2 save [PM2] Saving current process list... [PM2] Successfully saved in C:\Users\moose\.pm2\dump.pm2
Now, when our system restarts, PM2 will start whatever processes we had running when we ran
🐊 PM2 does a lot of things, most of which are out of the scope of this brief introduction. In the future we might cover PM2’s cluster mode, remote process management and more. Thanks for reading!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.Sign up