forever VS PM2

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.

There are plenty of ways to accomplish this: Docker, Kubernetes, Pulumis, etc., but I don’t like to add too much complexity. So for a basic app, I like to use PM2, a Node.js process manager with great features, including the ability to run our app in the background.

This project will consist of a single "index.js" file that you can deploy anywhere. I recommend using an Nginx reverse proxy and pm2 to keep the service running.

Your app should be running now. To be able to run the app in the background, I will use pm2. Stop your application using "Ctrl + C" and install pm2

https://www.npmjs.com/package/pm2 I found this package. It looks good and solves my problem, I think.

Usually, you have something that restarts it for you. This is what a "process manager" is for, e.g. https://www.npmjs.com/package/pm2 But in most more advanced systems, this is taken care of for you differently. E.g. lambdas are restarted automatically based on how many instances are needed. If you are in container-land, there's usually a health check endpoint on your server that gets pinged by the container orchestrator, and if there's no response, it will kill and redeploy the container.

Additionally, it provides many more features to manage and visualize the processes. More details on PM2 can be found in their official documentation.