Skip to content
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

Invalidating items on CloudFront #14

Open
ghost opened this issue Apr 16, 2016 · 3 comments
Open

Invalidating items on CloudFront #14

ghost opened this issue Apr 16, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 16, 2016

Hi there,

I have Jekyll with incremental build enabled but every time I run 's3_wesbite push' from the terminal, it is invalidating the entire site. It's costing me a small fortune in AWS fees. I thought incremental only touched the files that had changed.

What am I doing wrong?

Regards

@laurilehmijoki
Copy link
Owner

Can you share the source code of your site? Without confidential credentials of course. It's difficult to debug otherwise.

@ghost
Copy link
Author

ghost commented Apr 18, 2016

Sure. Thank you for helping me.

s3_website.txt

@laurilehmijoki
Copy link
Owner

Jason your config seems fine to me. Anyway there should be no optiob that causes the behaviour you are experiencing. I'm out of guesses. As a workaround, why not remove the CloudFront distribution id from the config and set the cache max age to something sensible? You can also generate cache-busted URLs (maybe https://github.com/tkareine/jekyll-minibundle will help you). That way you can benefit from CloudFront even without explicit invalidations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant