Feature: deploy configurations to have "env" variables

[koresar]

I wish I could avoid "env_staging": { "NODE_ENV": "staging" } lines in each of my (dozens) of microservices.

{
  "apps": [
    {
      "name": "app1",
      "script": ".",
      "env_staging": { "NODE_ENV": "staging" }
    },
    {
      "name": "app2",
      "instances": "1",
      "env_staging": { "NODE_ENV": "staging" }
    }
  ],
  "deploy": {
    "staging": {
      "user": "username",
      "host": "192.168.0.52",
      "ref": "origin/staging",
      "repo": "repo@url.git",
      "path": "/home/username",
      "post-deploy": "npm install && (pm2 stop all; gulp && pm2 startOrRestart ecosystem.json --env staging)"
    }
  }

Can we have default ENV variables per each deploy record? Like:

{
  "deploy": {
    "staging": {
      // ...
      "env_staging": {
        "NODE_ENV": "staging",
        "DB_CONNECTION_STRING": "mongo://db-server/staging"
      }
      // ...
    }
}

[Unitech]

Could you report this suggestion to : https://github.com/Unitech/pm2-deploy/issues

Thanks