How do I configure to upload a gzip instead of the assets about ember-cli-deploy-s3

[lukemelia]

By default, the gzip plugin gzips in place, adds a list of gzipped files to the deploy context, and the S3 plugin deploys the files and sets the right header based on the list on the deploy context.

I'm not familiar with codedeploy.

[jrdn91]

All codedeploy is doing is watching for revisions on a single asset in an s3 bucket, at which point it will start a deployment process which copies the zip file, unzips it and places the files in a specified location on disk and then moves on to the next instance in the auto scaling group until the revision has been rolled to all servers.

So to make that work all I need to do is upload a single zip or gzip file. But after installing ember-cli-deploy-gzip all the assets are still being uploaded as apposed to what I assumed it would do which is one gzip'ed file.

[lukemelia]

Ah, I see. That is not what ember-cli-deploy.gzip does. It zips files in
place. I would be open to a config option for ember-cli-deploy-gzip to
create an archive, or you could create a new plugin called perhaps
"ember-cli-deploy-archive" to do this.

On Thu, Dec 10, 2015 at 11:43 AM, Jordan4jc [email protected]
wrote:

All codedeploy is doing is watching for revisions on a single asset in an
s3 bucket, at which point it will start a deployment process which copies
the zip file, unzips it and places the files in a specified location on
disk and then moves on to the next instance in the auto scaling group until
the revision has been rolled to all servers.

So to make that work all I need to do is upload a single zip or gzip file.
But after installing ember-cli-deploy-gzip all the assets are still being
uploaded as apposed to what I assumed it would do which is one gzip'ed file.

—
Reply to this email directly or view it on GitHub
#36 (comment)
.

[jrdn91]

Yeah I thought about doing that, seems like it should be rather simple I would imagine.