You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. I have no idea and can't find instructions on how to either register or convert my ecosystem.config.js file
Describe the solution you'd like
I have an ecosystem.config.js file that works in development and Linux but have no idea where to put it and register it for pm2 service to use it.
From my understanding you just call pm2 start ./path/to/ecoFile. I am able to register my file but only if I don't specify a log/error path in my config
Is your feature request related to a problem? Please describe.
Yes. I have no idea and can't find instructions on how to either register or convert my ecosystem.config.js file
Describe the solution you'd like
I have an ecosystem.config.js file that works in development and Linux but have no idea where to put it and register it for pm2 service to use it.
Additional context
I have a working ecosystem.config.js file and don't know how to get it to work with the pm2 service.
https://pm2.keymetrics.io/docs/usage/application-declaration/
Here is what I have in my file:
module.exports = {
apps: [
{
name: "em-srv",
script: "/AppServer/mas-em-srv/server.js",
instances: "1",
exec_mode: "cluster",
instance_var: "INSTANCE_ID",
watch: false,
max_memory_restart: "2G",
autorestart: true,
wait_ready: true,
listen_timeout: 10000,
kill_timeout: 5000,
NODE_ENV: "development",
},
],
};
The text was updated successfully, but these errors were encountered: