restarting a running app does not respond to env changes

[neonstalwart]

there are 2 variations of this problem:

changing value of --env in the command does not use the new env

pm2 startOrRestart pm2.json --env foo
pm2 startOrRestart pm2.json --env bar

the app will still be using the foo env

changing values to be set via env does not use the new values

pm2.json

{
    "apps": [
        {
            "name": "server",
            "script": "server.js",
            "exec_mode": "fork_mode",
            "env_dev": {
                "NODE_ENV": "dev",
                "server_port": "8000"
            }
        }
    ]
}

pm2 startOrRestart pm2.json --env dev

update pm2.json

{
    "apps": [
        {
            "name": "server",
            "script": "server.js",
            "exec_mode": "fork_mode",
            "env_dev": {
                "NODE_ENV": "dev",
                "server_port": "8080"
            }
        }
    ]
}

pm2 startOrRestart pm2.json --env dev

at this point the app will still be using 8000 as the port.

[migg24]

This is also a problem for us, because it breaks 0-downtime deployment. You have to delete and then start the processes to refresh the ecosystem successfully.

[Tjatse]

This will be no problem with the dev-branch, be patient and waiting for the release. x)