Passing environmental variables to the script ... about pm2 HOT 4 CLOSED

The entire environment is passed to child scripts. I just tested now and it works

from pm2.

It works when using start, but at least for restart command it does not work, it keeps using the same environment as the one available when the app was initially started.
So if I have a script: app.js:

console.log(process.env[NODE_ENV]);

If I do:

NODE_ENV=test pm2 start app.js

It will output test, but if I then do:

NODE_ENV=development pm2 restart app.js

It will still output test.
Intended or not, seems a bit counter intuitive to me :).

from pm2.

actually it gets worse. The same effect as above is achieved if instead of restart you use start on a stopped process...

from pm2.

Can it be modified when the process is running? (assuming you change the ENV variables, then restart)

Matej Kramny

On Thursday, 9 January 2014 at 11:59, Manuel Astudillo wrote:

actually it gets worse. The same effect as above is achieved if instead of restart you use start on a stopped process...

—
Reply to this email directly or view it on GitHub (#33 (comment)).

from pm2.