I'm trying to deploy a node.js app on the cedar stack that uses MongoHQ. I
am not sure how what to include in package.json to get the mongo module
installed. If include mongodb: 0.9.1 under dependencies I get
mongodb@0.9.1 install /tmp/build_1q8sajeyt0jdx/node_modules/mongodb
Hi craayzie person,
You may want to take a look at http://redbot.org/
It tends to give some good pointers to debugging cache headers.
You may also want to implement some server side behavior to leverage the ETag
Also check out
On Tue, May 31, 2011 at 8:25 PM, craayzie flesh...@gmail.com wrote:
I'm setting a 'Cache-Control: public, max-age=300' response header per
the Heroku docs but when I request the resource, Heroku logs show my
app processing the request and subsequent requests for the same
resource continue to
I'm seeing the same behavior as craayzie. Redbot shows headers that
look correct:
HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Wed, 01 Jun 2011 20:16:01 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Last-Modified: Wed, 11 May 2011 19:35:02 GMT
Yup - I have the exact same setup. One dyno on Bamboo. I opened a
support ticket w/ Heroku yesterday. Will let you know what they come
back to me with. If anyone has any other suggestions let us know!
On Jun 1, 1:20 pm, Chris Hanks christopher.m.ha...@gmail.com wrote:
I'm seeing the same
I'm looking for guidance around how to log what our Rails app is doing/
serving without the $100/mo. advanced logging add-on. Our Heroku
budget for this project is $40-$50/mo. and it won't get off the ground
if we have to go the advanced logging route.
I've tried to over-ride the logger but I'm
Update - I commented out the line in question, pushed to heroku and it
worked, no errors. When I ran rake db:fixtures:load I had no problems
either. The file boot.rb now looks like this;
require 'rubygems'
require 'yaml'
#YAML::ENGINE.yamler= 'syck'
I don't know if this is the 'right' solution,
So after hearing back from support it looks like Varnish is caching
just fine it's just that they have a bunch of Varnish servers and the
chances of you hitting the same one twice is pretty low. Try firing
off 10 simultaneous requests and you'll see some of them served from
Varnish cache. Nice :)
I remember a couple weeks back we were strongly advised to send all traffic to
www. instead of a bare domain. What is the best way to ensure this happens? I
would do this at the Rack middleware level, but I'm getting frequent reports of
'server not responding' errors from users when they try
Huh. I remembered seeing somebody from Heroku say that they had their
Varnish servers set up in a hash ring, which I thought would mean this
kind of effect wouldn't happen, but I guess it does. It looks like
they have 10 Varnish servers going - if I use Apache Benchmark to hit
my server with 1000
10 matches
Mail list logo
