Different JSON structure needed to upload

[lazywithclass]

Different JSON structure needed to upload

[pifantastic]

Hi,

grunt-s3 is now a "multi-task", so the structure has changed somewhat. You'll need a top level options key for your global options, and then a key for each task. So the above should be rewritten like:

s3: {
  options: {
    key: 'key',
    secret: 'secret,
    bucket: 'bucket',
    access: 'public-read',
  },
  all: {
    upload: [{
      src: 'dist/scripts/main.min.js',
      dest: 'main.min.js',
      gzip: true
    }]
  }
}

In this example, I've named the task "all", but you can call it whatever you'd like. Now you can run this with either grunt s3:all or just grunt s3 (to run all defined tasks).

[lazywithclass]

If I try to execute the task with this structure it doesn't upload the file, with either grunt s3:all or grunt s3.
The output is this:

Running "s3" task

Done, without errors.

Without the file upload information.

[pifantastic]

Oh, whoops! My bad, the multi-task version of grunt-s3 hasn't been published to npm yet. That's my bad.

The README reflects the new multitask version of grunt-s3. I've actually created an issue to add docs (#41) for the non multitask version. I apologize!

Yes, your original configuration is correct for grunt-s3 v0.1.0. If you are using master, your configuration should look like what I posted above, using "multi-task"s.

[lazywithclass]

Ok great, thanks!