Update version when a cache sweep is performed #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Urgh, this is not going to solve production. |
|
I had my hopes up, your solution looked promissing. I didn't realize this will be also Production related issue 😭 |
|
Yeah, in production the application file will also no change fingerprint so browsers will keep using their cached version. Whatever solution we come up with has to ensure the fingerprint of applicatiom css changes in dev and prod (dynamic and precompiled) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #90
@dhh I think this is the simplest option we have. Use a timestamp as the cache version in development, and update it after every cache sweep. Only downside is that it will cause the browser to have to redownload every asset instead of just the one that was modified, since all digests will change.