Cache is rather persistent.. :)

[feelepxyz]

Hey!

Love it!
However, while playing around locally I'm having some problems figuring out how to make it reload the cache when eg 'view' files change.
Padrino seems to have a development reloader, which according to the conf is enabled by default on the development env.
But I can't seem to get it seeing changes, I manually have to delete the appropriate cache file to get it to rebuild it.

Note that I'm running the db from mongohq both locally and on heroku. If that may something to do with it. Seemed like a bother to do some kind of db push to heroku when authoring a page locally.. :)

Cheers
Philip

[bratta]

My first thought is that the view files should not be changing on production unless you deploy, and cache should be cleared on deploy.

On development, perhaps hooking the cache sweeping in on reload would work, I'll have to look into the possibility of that. Currently the cache system is undergoing a rewrite as it is horrible in the current code. I had hacked on the varnish support to get it quickly running on Heroku, but it is time to make it a bit more modular.

One thing I do plan on adding is a one-click cache sweep button in the admin ui to sweep on demand instead of only on page edits. That would make things a bit easier to manage too as you can hit that button after modifying your views if nothing else. I'll keep this issue open for now.