Hi Trevor,
Keenan is right in that Heroku doesn't support the X-sendfile method:
- http://devcenter.heroku.com/articles/rack-sendfile
The support team initially added this documentation last year after I
submitted an issue regarding problems I was having serving Sass-
generated files from
Thanks, Adam, for sharing that gist, and thanks again, Matthew, for
all your input!
We're hoping to be able to make heroku_rack open source soon, which should
make it a lot
easier to get in and tinker with stuff like this.
That would be great, but I think your solution of extending can_cache?
Hey Matthew,
Sorry for my late response. Our internet no worky.
No worries! Interesting to hear that there was an extraction of
heroku_rack, but it's since been taken down.
It seems to me likely that Heroku may have something like (but perhaps more
sophisticated than) use Rack::StaticCache,
!
Thanks for sharing your gist. I wish I had seen it last week! Let's
hope the Heroku team will enlighten us as to exactly what happens in
their stack when they see a call to Rack::File.
[1]: http://github.com/logicaltext/rack-bundle
--
You received this message because you are subscribed
According to the [caching docs][1]:
Anything that is served from the filesystem (a Rack::File) is cached for 12
hours.
That's great, but what if we want to use [Rack::StaticCache][2] (via
the rack-contrib project) to cache static assets for more than 12
hours? Does Heroku allow this? I tried
Hi All,
Has anyone had any luck using the path option in a `Gemfile` for a
vendored gem?
source rubygems.org
gem rails, 3.0.0.beta4
...
gem mygem, 0.0.1, :path = vendor/gems/mygem-0.0.1
This seems to work when I run my app locally in production mode, but I
get `const_missing`
