heroku restart inside app for clearing http cache

2010-04-13 Thread Chap
Need a button for a client to clear the cached version of a resource. As I understand it, redeploying and potentially heroku restart will cause this to happen. Is it possible for the app to restart itself? I wonder how people are handling this immediate cache expire problem. -- You received

Re: heroku restart inside app for clearing http cache

2010-04-13 Thread Carl Fyffe
There are much easier ways to expire a cache. The docs that explained how to create the cache more than likely will tell you how to expire it. Start there. On Tue, Apr 13, 2010 at 2:23 PM, Chap chapambr...@gmail.com wrote: Need a button for a client to clear the cached version of a resource.

Re: heroku restart inside app for clearing http cache

2010-04-13 Thread Chap
Thanks for responding Carl, I've been going over the docs and the only way it mentions forcing an expire is deploying: http://docs.heroku.com/http-caching#cache-purge-on-deploy On Apr 13, 2:29 pm, Carl Fyffe carl.fy...@gmail.com wrote: There are much easier ways to expire a cache. The docs that

Re: heroku restart inside app for clearing http cache

2010-04-13 Thread Carl Fyffe
That isn't forcing an expire, that is we clean up when you push, just to let you know. Please read this: http://tomayko.com/writings/things-caches-do And then this: http://guides.rubyonrails.org/caching_with_rails.html If you still can't figure it out, then come back. You should have a better

Re: heroku restart inside app for clearing http cache

2010-04-13 Thread Chris Hanks
Chap's question is pretty clear - he wants to flush a specific page from the http cache. Unfortunately, there's no way to do this on heroku right now. I'd love this functionality, too, but it just doesn't seem to be possible yet. What you can do, though, is set a low expiration on the cached

Re: heroku restart inside app for clearing http cache

2010-04-13 Thread Chap
Thanks for your help Chris and Carl. You both were right because I didn't fully understand how heroku's http caching was working (I thought it was only used by Varnish not the browser). I highly recommend the podcast RailsLab : Scaling Rails for anybody messing around with this stuff: