Allow to define environments which are used in tasks

[maxklenk]

I use these environments which allow me to execute the same task with different environments to deploy or build the application.

var environments = {
  development: {
    rev: false,
    deployBranch: false,
    constants: {
      ENV: {
        name: 'development',
        html5Mode: true,
        apiEndpoint: 'local.server'
      }
    }
  },
  testing: {
    rev: true,
    deployBranch: 'deploy/test',
    constants: {
      ENV: {
        name: 'testing',
        html5Mode: true,
        apiEndpoint: 'test.server'
      }
    }
  },
  production: {
    rev: true,
    deployBranch: 'deploy/production',
    constants: {
      ENV: {
        name: 'production',
        html5Mode: true,
        apiEndpoint: 'server'
      }
    }
  }


// ENVIRONMENT FLAG
var env = environments.development;
for (var index in environments) {
  if (!!argv[index]) {
    env = environments[index];
  }
}

[sebastianhenneberg]

I'm not completely sure if this functionality belongs into the tasks. Don't you think it would be better to handle the environment switch in the userspace (gulpfile.js or gulp_config.js)? We could consider some convenience tasks for the environment selection.

[maxklenk]

The code I pasted should be inside the gulp_config.js, it just allows you to define different configurations. The tasks just access config.env.

[sebastianhenneberg]

I know, I looked it up the private repo. However, then I do not understand the intention of this issue.