load configuration from /etc/default/pm2

[shaharmor]

fixes #1844
fixes #1845

[Unitech]

Looks great, thank you!

[Unitech]

I did some test, unfortunatelly environment variables loaded from /etc/default/pm2 are not passed to the pm2 command :/

because of the su - command: https://github.com/Unitech/pm2/blob/master/lib/scripts/pm2-init.sh#L55

I'm trying some stuff, if you have any idea it's welcome

[shaharmor]

How did you test it? i am using something similar in production now.
Maybe its because i am using root user

[Unitech]

Replace:

su - $USER -s $shell -c "PATH=$PATH; PM2_HOME=$PM2_HOME $*"

By:

su - $USER -s $shell -c "env; PATH=$PATH; PM2_HOME=$PM2_HOME $*"

I've added PM2_KILL_TIMEOUT in /etc/default/pm2 and doing service pm2-init.sh restart, the variable is not present when doing the env command

[Unitech]

I found the solution, when importing variables we must do set -a then when we finished we do set -a

On the su command we just need to pass the -m option to preserve environment variable

But now the problem is that if someone use the /etc/default/pm2 file for configuration variables, PM2 is not aware itself of this file, so I will continue to think about this way of configuring PM2

[shaharmor]

I'm not sure this is supposed to be used to set environment variables, but instead just bash variables

[shaharmor]

Its not supposed to replace PM2 environment variables (Which for themselves should move to the app json), but just startup variables like ulimit

[Unitech]

Yes I was thinking that it could be a good way to configure some internals PM2 variables but yes you are right, let's keep the /etc/default/pm2 for startup variables