Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Consider preparing for CloudFront nightmares #27

Open
toolness opened this issue Jun 28, 2017 · 0 comments
Open

Consider preparing for CloudFront nightmares #27

toolness opened this issue Jun 28, 2017 · 0 comments

Comments

@toolness
Copy link
Contributor

This app really doesn't need tons of caching because it's going to have so little traffic, but if it ends up being hosted somewhere other than a subdomain of app.cloud.gov, that means it's going to be fronted by CloudFront, which means nightmares. See e.g.:

We might also want to use Whitenoise's compressed manifest static file storage so that it gives every static asset a unique URL based on its hash. Or we could just tell whitenoise to serve its static assets with max-age=0 too, I guess.

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

No branches or pull requests

1 participant