PM2 dev and prod environments on same server

user_101254 0
Viewed 696

I have a dev and prod instance of a microservice running on one machine. My ecosystem file gives them the same name. PM2 will not start the second instance when the first is running due to the name (presumably). Any ideas for a workaround here?

pm2 node.js
2 Answers

Thanks for the help... I ended up with this:

require("dotenv").config();

module.exports = {
  apps: [
    {
      name: "app-" + process.env.environment,
      script: "./app.js",
      max_memory_restart: "150M"
    }
  ]
};
user_1012540

Pm2 do not sensitive filename because the name is usual for human not for PM2 process.

The usual mistake:

  • Two script try to listen one port.
  • conflict between scripts & resources.

The solution is start first process with pm2 and second process normal start with nodejs and you can see the log and error if not start, or started successfully then start second process first, first process second.

and you can use pm2panel for easily add or remove process in pm2.

user_18230030
Related