Rails with Twitter Bootstrap: Still Serving the Old Asset

Question

Here you can find nuts. I am developing a rail application and I am using the twitter-bootstrap-rails pearl to enable Twitter Bootstrap styles in my application. This stone generates a file called "bootstrap_and_overrides.css.less" in the app / assets / stylesheets file, which I used to change some boot parameters and included my own CSS overrides.

Everything is working fine until today. For some reason, the changes I make to this file today are saved to the file, but Rails still maintains the old version of the file! I searched and did not find any precompiled versions of the file anywhere (nothing public / assets) ... only the one that was changed in the properties / styles that I changed. Everything looks fine, since the directories in the application go, but then when I start the rail server, load the page and use the element inspector to view the stylesheets, it uses the old version of "bootstrap_and_overrides.css.less", with the rules that I deleted. I turned on the cache in my browser and tried it in 4 different browsers, so I'm sure this is not the result of browser caching.

The rail resource pipeline seems to be for a version of the file that does not exist! Anyone have any ideas why this might happen?

Answer 1

Corrected.

The resource pipeline stores the cached version in tmp / cache.

I ran rake tmp:clear , which deleted all the files there, and then the rails served the * bootstrap_and_overrides.css.less * version that I wanted.

Why the cached version suddenly stopped receiving updates is up to me. Arrghhhh!