Skip to content

Implement cache busting for our own static files #23

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

Merged
merged 1 commit into from
Jan 31, 2025
Merged

Conversation

JelteF
Copy link
Collaborator

@JelteF JelteF commented Jan 31, 2025

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.

@JelteF JelteF merged commit 57361ad into main Jan 31, 2025
JelteF added a commit that referenced this pull request Feb 16, 2025
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.
@JelteF JelteF deleted the cache-busting branch February 27, 2025 20:22
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

Successfully merging this pull request may close these issues.

1 participant