Implement cache busting for our own static files #23
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.
Browsers cache static files. That's obviously good. Currently it results in our we change files server side, users don't always see them.
This generates a GET parameter that's unique per startup of the python process to bust the cache of the client, so that it pulls in possibly updated JS/CSS files. Obviously this is a bit more often than necessary, but caching should still work most of the time and our custom css and js files are tiny anyway. At least the changes that are made will now be reflected to our users.