the Heroku and Radiant
caches. I've found that just doing step 1 seems to be enough, most of
the time.
As an aside, I've found Radiant running on Heroku to be a particularly
nice combination. Heroku's use of Varnish works exceedingly well with
Radiant, once you know how to bust the caches :). Once
Sean,
To round this discussion off, the Heroku docs say that the
Cache-Control header should be set to control the length of time a
page should stay in the cache:
http://docs.heroku.com/http-caching#caching-dynamic-content-by-age
Is it possible to control the max-age header in Radiant? If so,
2009/11/30 Sean Cribbs seancri...@gmail.com
That seems correct. I'm not sure about their other infrastructure, but
as of the current version, doing a hard-refresh in your browser will
cause the page to be purged from the cache as well.
Thanks Sean. When you say as of the current version,
I've been developing a Radiant-powered site on Heroku and have been having
difficulty with caching. When I save a page, the change will (usually) fail
to show up. Obviously I am aware that both Radiant and Heroku do some (quite
aggressive?) caching, so I was wondering if anyone could offer some
That seems correct. I'm not sure about their other infrastructure, but
as of the current version, doing a hard-refresh in your browser will
cause the page to be purged from the cache as well.
Sean
Charles Roper wrote:
I've been developing a Radiant-powered site on Heroku and have been having
