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 > 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 advice > for when developing a site and the need for aggressive cache clearing is the > priority. > > I've found logging into the heroku console and then clearing the cache to be > quite effective: > > [ D:\Users\charlesr\Documents\My Dropbox\Projects\radiant_roast ] > >> heroku console >> > Ruby console for foobarbaz.heroku.com > >>> Radiant::Cache.clear >>> > => [#<Radiant::Cache::EntityStore:0x2b5c98de4a20 > @root="/disk1/home/slugs/89730_0ada040_1fcc/mnt/tmp/cache/entity">] > > > Is this the best way of tackling a cache refresh, or should I be doing > something else? > > Cheers, > Charles > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
