A little bit of further information for Radiant users on Heroku. This is from Morten at Heroku:
--- I am not familiar with the particulars of Radiant caching. However, Varnish can't be run clustered so our HTTP caching layer consists of n individual Varnishes. You may see results propagating across the Varnishes giving you an occasional stale hit. This is normal, and in full usage on a busy site it's a very minor issue because it only takes one request for the cached copy to update. Also, the only way we have to purge the HTTP cache is heroku restart. --- So, when I save a Radiant page/layout/snippet, the general process I follow is this: 1. In the Heroku console, issue the Radiant::Cache.clear command and hard-refresh in browser. 2. If changes still don't show, issue the heroku restart command and hard-refresh again. This seems to be a pretty robust way of clearing 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 a page is cached in Varnish, the backend doesn't get touched, so even with a free 1-dyno account, you get really great performance. This is possibly the most up-to-date tutorial, if anyone is interested: http://j.mp/3ocDje [random facts girl: Radiant Heroku… getting your Radiant App live on Heroku in about 10 minutes.] Charles _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
