Reputation: 9393
I have a Jekyll bootstrap based blog hosted on Github pages.
My problem is: Every time I change something on my web page, I have to forcefully reload the page (CTRL + R) to see the changes.
Jekyll or my browser does not seem to realize that there is a newer version available to send out.
How can I configure Jekyll to better handle this?
Upvotes: 30
Views: 3239
Reputation: 34939
There are a couple of jekyl plugins to handle assets cache busting.
https://github.com/ixti/jekyll-assets/
http://matthodan.com/2012/11/22/jekyll-asset-pipeline.html
I tried jekyll-assets and it's pretty nice as it manage all kind of assets with an md5 version number.
Before I use to append a string to my css links at compilation time.
<link href="{{ ASSET_PATH }}/css/global.css?{{ site.time | date:'%Y%m%d%U%H%N%S' }}" rel="stylesheet">
Upvotes: 6
Reputation: 8545
You can add these meta tags to your html to disable browser caching for your pages.
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="-1" />
Upvotes: 3
Reputation: 2718
If you want to bypass the cache on static resources you could change the name of the file each time you push it. This will make the browser get the new resource since it won't know anything about a file with a new name.
For example:
Old file name: project.css
New file name: projectv01.css
Or whatever you would like.
Upvotes: -1