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

Caching #31

Open
mads-hartmann opened this issue Jun 21, 2017 · 3 comments
Open

Caching #31

mads-hartmann opened this issue Jun 21, 2017 · 3 comments
Labels

Comments

@mads-hartmann
Copy link
Collaborator

mads-hartmann commented Jun 21, 2017

We need to figure out how caching should work:

  • cache headers
  • CDN expiration
  • how to configure it?
  • should we flush when deploying?
@mads-hartmann
Copy link
Collaborator Author

It seems that if we enable versioning for the buckets we get some nice cache invalidation for free. http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#Invalidation_Expiration

@mads-hartmann
Copy link
Collaborator Author

@skovhus
Copy link
Collaborator

skovhus commented Jul 18, 2017

I've implemented same caching as https://surge.sh/help/using-lucid-caching-automatically ... And think that is fine right now. : )

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

No branches or pull requests

2 participants