Thanks Oren that worked
Anyone interested can simply test by hitting the index on this
controller
class ThingsController ApplicationController
require 'rubygems'
require 'RMagick'
def index
img = Magick::Image.read(#{RAILS_ROOT}/public/images/
rails.png).first.scale(5).to_blob
RUBY_PLATFORM works for me, fyi
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit
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
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.
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
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
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
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: