more flexible config

[sebv]

Right now configuration is not flexible, would be good to be able to declare several server config or even rename the task to server for example, without having to for your own task.

The change below would let you configure like this:

    connect: {
      dev: {
        port: 3010,
        base: 'app/public',
        keepalive: true
      },
      dist: {
        port: 3011,
        base: 'dist/public',
        keepalive: true
      }
    },

var config = target ? grunt.config(['connect' , target]) : grunt.config('connect');
var options = grunt.util._.defaults(config, {

The change below would let you change the task name (maybe there is a better way)

var config = grunt.config([grunt.task.current.name].concat(grunt.task.current.args));
var options = grunt.util._.defaults(config, {

[shama]

You should be able to specify multiple targets and reference them with grunt connect:dev, grunt connect:dist or grunt connect for all targets.

You can also rename tasks with grunt.renameTask or simply register a new task to point to one or more other tasks: grunt.registerTask('server', ['connect']);

[sindresorhus]

Also, the option thing is already built into grunt 0.4.

Just do:

connect: {
  options: {
    keepalive: true
  }
  dev: {
    options: {
      port: 3010,
      base: 'app/public'
    }
  },
  dist: {
    options: {
      port: 3011,
      base: 'dist/public'
    }
  }
},

[sebv]

Yeah but did you test it? It doesn't seem to work.

It is due to the way you retrieve the config:

grunt.config('connect')

It doesn't follow the task definition, if the task isn't called connect, the config is not used.

Edit: Am using grunt 0.4.

[shama]

Oh you're right @sebv. It looks like that changed in this commit. I'm not sure why.

[sebv]

Better ask sindre for advice, there should be guidelines from grunt on the best way to get the config.

But I've debugged it, the problem now is that your config return a complex configuration object rather than flat options.

[sindresorhus]

@cowboy Why the change to not support targets?

[cowboy]

I don't think it ever supported targets. But it totally can, now's the time to do it! Want to make a PR?

[sindresorhus]

@cowboy I'm pretty sure it did before this commit ccd5ab9#L7L21

[cowboy]

Let me know what you think of my changes!

[sebv]

Thx @Cowboys it works fine. Maybe, just for this task, it'll be worth explaining in the doc how to rename the task to server. If you are migrating or doing things like this, it's nicer to be able to keep the server task name.