Replies: 3 comments
-
Just curious - why can't browser caching solve the issue here? I am pretty sure the static assets that come with each Wagtail release have a hash in the URL so the files can be cached heavily. Maybe something needs to be adjusted in Django or your CDN to ensure the right cache headers are getting added. I might be missing something here but I thought a local cache of known resources is what the browser already does. |
Beta Was this translation helpful? Give feedback.
-
Yep, I think what you're describing is the same as setting a far future Expires: header on static files at the web server level. |
Beta Was this translation helpful? Give feedback.
-
For static file serving like this, I highly recommend using whitenoise to achieve this. Once implemented, using the For an example of whitenoise in action, take a look at the static files being loaded on wagtail.org, most importantly their |
Beta Was this translation helpful? Give feedback.
-
We have thought of loading the static files (from the local machine) instead of (from the server)..
the idea came as an urge of a project that our client is demanding lots of ERP Apps in wagtail admin, and we believe that the we better let the idea to be officially managed by the core team for global editors..!
the extension does the following:
the extension has the following config options:
related discussion/issues:
all discussions that related to performance and UX (please tag them in comment)
Beta Was this translation helpful? Give feedback.
All reactions