mod-rails

Unicorn has OobGC rack middleware that can be used to run GC.start after a certain number of requests. Is there a similar sort of thing in Phusion Passenger? Phusion Passenger 4 officially introduces an out of band garbage collection mechanism. It's more flexible than Unicorn's by allowing any arbitrary work, not just garbage collection. http://blog.phusion.nl/2013/01/22/phusion-passenger-4-technology-preview-out-of-band-work/ Hooking into PhusionPassenger::Rack::RequestHandler#process_request() is the only mechanism I have found. To do this in a similar way to the Unicorn OobGC, you can use

Am not able to upload a 8.4 MB file, in a passenger app behind apache. Transferring the same file via scp took 4.1 minutes. Error backtrace: [ pid=10222 file=ext/apache2/Hooks.cpp:727 time=2010-05-18 07:13:14.842 ]: Unexpected error in mod_passenger: An error occurred while receiving HTTP upload data: Connection reset by peer (104) Backtrace: in 'boost::shared_ptr Hooks::receiveRequestBody(request_rec*, const char*)' (Hooks.cpp: 1084) in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:459) NOTE:user had not cancelled or anything. He was on firefox :-) other errors seen in the logs are: [

I run an instance of a rails application that is developed by another team. Back when I started, the common way to deploy Rails apps was to use Mongrel behind Apache, and that's the configuration that that team used for their own instances. Since I'm a Windows guy, and since both Apache and Mongrel can easily be set up as Windows services, I used a (virtual) Windows box and set up everything there. I guess since than things changed in Rails land. Mongrel has stagnated (at least that's my impression of the common perception). The team developing my app has switched to using mod_rails a while

I am in the process of setting up a server to run a Ruby on Rails application on Fedora 12, using Passenger. I am at the stage where I've installed Passenger, set it up as prescribed, but get the following errors when I restart Apache: [Wed Jan 13 15:41:38 2010] [notice] caught SIGTERM, shutting down [Wed Jan 13 15:41:40 2010] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0 [Wed Jan 13 15:41:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Jan 13 15:41:40 2010] [error] *** Passenger could not be initialized because of this

Does anyone know a good solution to limit the file upload size when running a Rails application with Passenger/mod_rails. The request should immediately be declined, so that the file doesn't get transferred to the server. The solutions I've found so far all describe how to patch Mongrel to implement a limitation, but I have to use passenger with this application. Or if you're using nginx with passenger, add in the server block: server { client_max_body_size 100M; } http://wiki.nginx.org/NginxHttpCoreModule#client_max_body_size You may cap the upload size via Apache using the LimitRequestBody