I'm seeing the following when pushing to Heroku:
Configure Rails 3 to disable x-sendfile
Installing rails3_disable_x_sendfile... done
What is this about? Is there a way I should configure my app to avoid seeing
this message?
--
You received this message because you are subscribed to the
Hi Trevor,
config/environments/production.rb line 12
# Specifies the header that your server uses for sending files
# config.action_dispatch.x_sendfile_header = X-Sendfile
# For nginx:
# config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect'
# If you have no front-end server
I have:
config.serve_static_assets = true
...but I don't have anything with:
config.action_dispatch.x_sendfile_header
...at all. Perhaps you are doing something unnecessarily in my case? You can
view my app teamlab yourself on Heroku if you like. I can file a support
ticket if necessarily.
Hello Trevor,
Web servers (e.g.: Apache) is tuned for serving up static files.
Ruby (e.g.: mongrel) is not as efficient at serving up static files.
But sometimes, your ruby code generates a file that needs to be streamed. Or it
uses logic to determine the name of an existing file that needs to
I'm trying to deploy a simple skeleton Rails 3.0.5 (and Ruby 1.9.2)
app to Heroku, but encounter the same error when I open the website
and when I try to migrate the db. I created the Heroku app with heroku
create --stack bamboo-mri-1.9.2. Everything works locally.
Code:
I have no idea what your problem is.
But if you are looking for places to start,
root :to = pages#index
in config/routes.rb has the clue '#' in it.
Just a suggestion.
jeff
On Sun, Mar 20, 2011 at 7:46 PM, Curious Yogurt
starempireel...@gmail.comwrote:
I'm trying to deploy a simple
On Monday, March 21, 2011 12:06:35 PM UTC, Keenan wrote:
So you need to tell rails to not use the handy X-sendfile header and stream
the file through.
How this affects Heroku?
The web server is running on a different machine than the dynos. So
X-sendfile doesn't work.
So they modify
Thank you! Actually it did fix itself, I broke something this morning and
suddenly I received an Email from Exceptional.
For the archives: there is nothing to install or to add to your code, just
add the heroku add-on.
Markus
--
Ruby on Rails CommunityGuides: http://www.communityguides.eu
On
Tom,
You can start with the new relic add on, and watch response times, and queue
depth.
What I've done in the past is run some load tests through a local deployment
to get a sense of how many requests the app can handle on a 'similar' stack
(postgres, thin, etc).
Then I run the same load tests
I've been doing a lot of security work lately, making sure a rails app meets
the security standards of a major financial institution.
In addition to input scrubbing, output escaping, and making sure exceptions
don't reveal too much data, I've had to implement basic captcha, to make it
harder for
In addition:
plug
Try http://blitz.io (just announced our public beta), run a bunch of
load tests while monitoring with new-relic. For rails and sinatra
routes, you can easily parameterize the 'params' part of the URL so
you test with different values hitting the DB.
/plug
K.
---
http://blitz.io
11 matches
Mail list logo