similar to: Deploying Rails with Pound in Front of Mongrel, Lighttpd, and Apache

I have an existing rails application on lighttpd and I am trrying to upgrade to mongrel for the enhanced scalability it offers. I am running mongrel 1.1.1, rails 1.2.5, lighttpd 1.4.13 and ruby 1.8.5 Everything is working great except request.remote_ip returns 127.0.0.1 or 192.168.0.102 (the internal network address of the server running lighty). I''ve seen some older posts about

I''ve messed with Lighttpd, Litespeed, Apache, etc. All took too much "thinking" and trial and error to get my RoR apps up and running on a clean Linux system. (Note: I''m not saying these are BAD, just that they took me too much time to get going) This weekend I put some time into Pound and Mongrel and ended up getting that up and running in a very short amount of

This might not be a mongrel question so much as an IIS question, and if so, my apologies. I''m needing to switch a (ASP.NET) web application that''s running behind a firewall appliance on IIS on port 8443 under SSL to a rails web application -- a mongrel instance (and perhaps later apache or lighttpd with new mod_core_prox in front of mongrel) on a different server. I remember

Hi! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =

Hello, I''m experiencing a strange, but very bad behavior with Mongrel 0.3.13.4 and Pound 1.8. Every 6 hours or so one of our nine (not consistent on which one) application servers ( each one running several mongrel processes ) will start leaving lots of socket connections with pound open. This leads to "Too many open files" errors. I''ve set pound to close connections

I was about to write a long post about how I couldn''t get request.ssl?to work in Rails behind Pound and Mongrel, but then I figured it out. In your pound.cfg file, just add: HTTPSHeaders 1 "X-Forwarded-Proto: https" Assuming you''ve got Pound working correctly with SSL, this will giveRails the header it''s looking for. If there''s any interest in a Debian

I want to host a rails app at mydomain.com/railsapp. For technical reasons I have to leave mydomain.com on apache. This means that I need to tell apache to proxy only requests for mydomain.com/railsapp to lighttpd. I have deployed in a situation like this before around a year and a half ago but it was a real pain. Lighttpd and rails have matured a lot in the year and a half since I did

I''ve been using a homegrown system to do billing for my site. Right now I want to add a couple things, but I''m not sure I want to actually have to work on this billing system. Seems like it''d make a lot more sense to just use an existing package like ModernBill [1]. I''ve never used PHP on lighttpd, never needed to. Not sure if MB can run on it, or how well

Hi guys, I''ve been chasing a problem in my web-stack: Lighttpd -> Mongrel -> Rails, and found a problem with the interaction of Lighttpd and Mongrel. If a request takes more than 5 seconds, Lighty will retry it - and then the requests / responses get mixed up in Lighty and it returns a bad response to the client. Not good. I''m convinced that the problem is

Is anyone using the setup described at the Rails blog? http://weblog.rubyonrails.org/2006/7/3/pound-makes-lighty-and-mongrel- play-nice I''m using it in production, and the only problem I have is the same as people have described in the comments over there, namely that Rails thinks all requests come from localhost. See http://isabont.com/requestinfo for the headers. Any

Hi guys, I had mongrel_upload_progress working very sweetly on my dev machine, where mongrel was acting directly as the webserver. But when I went to production it stopped working. The Problem: On our production server we use Lighttpd, and it looks like lighty is buffering the whole upload and then giving it to Mongrel in a big chunk. This pretty much screws up the whole point of

Hi, i''m using to ziya to display some graph. If i use it running mongrel as single instance all work good (very slow but work). If i try to use it with pound as htto proxy ziya charts wait forever for data...that never arrive. If i check the mongrel log it seemes to make queries on the database and retrieve data,but nothin appera. Anyone have an idea on how i can solve this problem?

I am wanting to one run instance of lighttpd, many many instances of mongrel. I also need ssl but only for one of my sites. I understand that Mongrel does not play with SSL so I am forced to use Lighttpd. I think that lighttpd only handles ssl or non-ssl on any given instance. Is there a way for me to accomplish my goal of one lighttpd with multiple mongrels and the occasional ssl connection? --

Hi All, I''m experiencing a problem when using pound with Rails. My set up is I have a machine acting as a load balancer running Pound. This listens on port 80 and directs requests with a particular URL to two backend servers both of which are serving my rails app using mongrel cluster on ports 9000,9001 and 9002. There is a problem with sessions even though I am storing the session data

Right now you can use either Pens/Balance/Pound to put in front of some Mongrels and it works really good (easy to setup too!). I got to thinking, would it be possible to mimic what Pens/Balance/Pound does in pure Ruby (yeah, I know the answer is yes)? I guess I''m looking for a starting point. Does one simply write an HTTP listener that then redirects the calls to Mongrel? Is

I have been trying to get Lighttpd working.... we have been using webrick, but want to move to a production quality web server. I followed the instructions found here : http://brainspl.at/pages/rails_stack We are developing on windows and deploying to Fedora Linux. We''re using rails 1.0. The build actually happens on the windows box and using ant transfers the code to the Linux box.

Finally! I''ve released Mongrel 0.3.13 OFFICIALLY to the public for better or worse. This release is pretty huge compared to previous releases. It''s got oodles of fixes, design improvements, hosting enhancements, win32 changes, and the release even works with the latest cygwin. Read all about it at http://mongrel.rubyforge.org/news.html GETTING 0.3.13 Most people do this:

I know most people use pound, but has anyone tried using ultramonkey as a load balancing solution between a cluster of mongrels and lighttpd? Thanks, Ray -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email

Hi Folks, We''re moving from a single lighttpd-hosted Rails box to a Apache/ mongrel cluster. In lighttpd, mod_compress had a very nice feature: if there''s a static file, it would compress it in a user-specified compress folder. If the file hasn''t changed, it would just serve out the compress file; if the file has changed, it would recompress it and serve it out.

I recently moved an app. from lighttpd + fastcgi to apache 2.2 + mod_proxy_balancer + Mongrel. On lighttpd, I was using basic authentication with a configuration like this: auth.backend = "htpasswd" auth.backend.htpasswd.userfile = "/path/to/htpasswd" auth.require = ("/" => ("method" => "basic", "realm" => "My