You can clone with
I'm trying something that is not documented. The scripts to push resources to S3.
It pushed all unprocesses resources from /css, /images, /js, but it did not push processed resources (cached-resources and zipped-resources outputs).
Is there any configuration I should make?
Indeed, this is currently a work in progress... Even if we use it for our apps in prod.
Each time we push a new release in production, we push all the static assets on S3.
We don't use the zipped-resources plugin.
I made some minor changes in the CDN plugin to be able to share plugin resources hosted on S3 :https://github.com/benorama/grails-cdn-resources
But I don't know if it is the best solution.
It looks like people use directly their Grails app with the cached-resources as an origin for their CloudFront distribution.
Any opinion on this?
I'm using elastic beanstalk to do zero downtime deployment of new versions. So when I create a new environment of a new version, aws creates a new ELB. So I can't create a new cloudfront distribution every time a deploy a new version (several times a day).
I'm stuck with S3 based cloudfront distributions.
Still looking for a solution for uploading zipped and hashed resource. I'm not very familiar with resources plugin source code. If you give me some pointer I can try to implement it and make a pull request.
FYI, we have move the S3 resources deployment scripts to a new repo:https://github.com/agorapulse/grails-s3-resources
This new version will take into account zipped/minified resources.
It is still in beta stage and not published yet on Grails.org.
If you want to give it a try let us know.