PM2 VS forever

GitHub: PM2 Repository

You can run the command pm2 status to check if both servers are online and running, as shown below. To learn about all of the other PM2 commands, read the documentation on PM2 Process Management Quick Start:

For teams using NGINX+PM2, moving to NGINX + HashiStack is a more robust and flexible solution—a great fit for startups looking for scalability without the complexity of Kubernetes.

PM2 Documentation - https://www.npmjs.com/package/pm2

What we wanted was something like a supercharged pm2, but multi-node with good support for both docker and binaries.

6. PM2

More pm2 commands here

Start by registering the app using the official guide.

Run the application using PM2 (ref: Process manager for Node.js)

Have you checked out https://github.com/foreversd/forever

Forever A simple CLI tool for ensuring that a given script runs continuously (i.e. forever)

Also, if you want node red to run on startup, you can use PM2 or forever to make that happen.

There is no accountability. From the license (MIT) https://github.com/foreversd/forever/blob/master/LICENSE#L13...

> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, [...]

You can fork it, if you wish. You can maintain a public fork and even accept patches from the community, or not accept patches, or only maintain a private fork and not share it with anyone.

Also, it looks like it's in a semi-zombie state. They even encourage to use other programs:

> A simple CLI tool for ensuring that a given script runs continuously (i.e. forever). Note that this project currently fully depends on the community for implementing fixes and new features. For new installations we encourage you to use pm2 or nodemon

This is great but, I'd rather not have a console left open 24/7, so I decided to use the forever package to run my script in the background:

To use at the same time multiple NodeJS servers you can use forever. I think you can do it without forever, using the normal NodeJS console, but I wasn't able to.