-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalidate existing file when it was changed #9
Comments
I've never used grunt-s3 does it provide a list of updated files? |
I use aws-s3 (tried s3 and had issues). It does output to console which files are changes, so if it doesn't provide that information in a return somewhere, I suspect it would be fairly trivial to get it. I could use this too. |
|
any examples on how to use aws_s3_changed in the gruntfile? |
As far as i understand amazon consider wildcard cache invalidation as one invalidation cache request, even if there are thousands files. So if you afraid that you will be charged for 1000 cache invalidation requests while invalidation of folder with 1000 files then no. What goal is there then? Prevention user browser from realoading additional files, that's browser cache problem then, or no? |
@rantiev that's what I ended up doing |
@rantiev I want to be sure I understand because I think not. Are you suggesting that when one file file has changed, one should invalidate all files? |
I manage to make it work. The trick its in creating a dinamyc task.
invalidatedfiles its our dinamyc task;
|
Hi Steffen,
I use grunt-s3 for publish my build and I use sync with { verify: true } for upload new or changed files only.
Is it possible to invalidate only changed files?
The text was updated successfully, but these errors were encountered: