similar to: Super simple web proxy.

This is not directly a Rails question but you lot seem the best to ask... I have a strong feeling we will be developing future apps in Rails (Ruby fans are slowly starting to outnumber cynics in my office) so I want a web server plan that will be appropriate for that. We have just bought two new web servers I want to turn into a load-balanced, redundant pair. As well as any Rails

i have a very simple lighttpd config that just forwards with mod_proxy some requests to different hosts lixe this: server.modules = ( "mod_proxy", "mod_rewrite" ) server.port = 80 server.pid-file = "/var/run/lighttpd.pid" server.errorlog = "/var/log/lighttpd-err.log" server.document-root = "/var/www/htdocs/"

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

I was using lighty+fastcgi before, and it was working pretty well, but I decided to move to Apache+mongrel because I really really like Mongrel. Well now I found out about lighty+pound+mongrel [1] and I think I''m going to give that a shot. I definitely prefer lighty to Apache - it''s pretty ridiculous how much fewer resources it uses. Anyway the only thing I''m going to

Zed / List, On my workstation I''m running lighttpd 1.4.11 and mongrel 0.3.12.4. Here are my proxy settings: proxy.debug = 0 proxy.balance = "fair" proxy.server = ( "/RailsAppSample" => (( "host" => "127.0.0.1", "port" => 1337 ))) I can access http://localhost/ (default lighty welcome page) and http://localhost:1337/

Hi, I''ve noticed an issue (or what I think is an issue) with mongrel_cluster: in the config file, I tell it to store pid files in / tmp/ and when I start it they get saved there, but when I run restart or stop, it says it can''t find pid files. Problem being: it looks for pid files in /path/to/my/app/tmp/. Is anyone else aware of this? I have lighty forwarding to pound

All, I realize this was probably off-topic (not really mongrel-centric) -- my apologies. I "solved" the problem by appending to my Environment.rb: ActionController::AbstractRequest.relative_url_root = "/RailsAppSample" How come that doesn''t serve up the default "public/index.html" ? It caused a Routing Error for "", so I added a temporary

Sorry if this get listed twice. Evolution hates me today. -------- Forwarded Message -------- From: Charlie Bowman <charlie@castlebranch.com> To: rails@lists.rubyonrails.org Bcc: Drew Stinnett <drew@castlebranch.com> Subject: Re: [Rails] more fcgi problems on apache Date: Tue, 30 May 2006 15:43:09 -0400 The decision isn''t mine. I''m just the programmer. This is

Hi mongrel-users, Just a heads up for apache2.2 mod_proxy + mongrel + rails users: If you have a line like this in your source (because you''ve done a poor job maintaining your code and reading the API docs): render ''foo'', :layout => ''bar'' You might expect it to do what it says... but it actually sets deprecated_status and ends up setting

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

Hello, I have an issue I am having trouble figuring out. I have a Rails app running through lighttpd which is accessed through an Apache proxy. My apache config: <location /rails/> ProxyPass http://localhost:81/ ProxyPassReverse http://localhost:81/ </location> RewriteEngine On RewriteRule ^/rails/(.*) http://localhost:81/$1 [P] So when apache sees /rails/ it

Hey all First off, ive just switched to using mongrel_cluster and pound - its working a treat! Its far far faster than fast-cgi: operations that took a few seconds on fcgi now are almost instant with mongrel. Excellent! However, I''ve been trying to decide how best to utilise my equipment most effectively. I have a dual pro 3Ghz Xenon with 2GB RAM, and the server will be running a few

I have an action which requests another URL from the same site (for testing purposes), but it keeps timing out. If I use an off-site URL, the action works fine. I also notice that I''m only able to request one page at a time from my server - the rest just spin until the previous requests complete. Is this some setting in Lighty, Mongrel, or my browser (Firefox - I played around with

On httpd I use ProxyPass and ProxyPassReverse to forward requests to webrick and mongrel. How can I do this same thing using Lighty and Mongrel? Thanks, Joe -- Posted via http://www.ruby-forum.com/.

Gang- We are getting ready to launch our ROR application; the last item remaining is the deployment platform. For testing, we had used Apache + MOD_FastCGI. I am not that impressed with it; sometimes it has strange effects. For example, when we start the application, for about 5 minutes or so, the app is very unstable and it gets better over time. My questions is .. should I go with (1)

Hi all, I''ve just spent some time going through trying to get mongrel & apache 2.0 working with mod_proxy. I thought I''d share what I''ve found in case someone is going through the same exercise. Of late, I''ve been using mongrel (lovely, btw) to run my rails apps. Since I have a couple of different rails apps running on the machine, I thought it be nice to

On 8 April 2016 at 09:52, Morgan Cox <morgancoxuk at gmail.com> wrote: > https://www.ovirt.org/ ? > > On 8 April 2016 at 09:23, FrancisM <francis at mytechrepublic.com> wrote: > > > Hi All, > > > > Is there someone out there using web browser to manage multiple KVM > > host servers right now in checking the MIST.IO Cloud platform and there > >

Hi everyone, Recently, I''ve been reading about different deployment environments for rails and mongrel. One configuration I''ve started seeing is apache -> pen -> mongrel cluster. See http://errtheblog.com/post/35 as an example. Can someone explain to me the benefit of using Apache and Pen as opposed to either using apache as a load balancer or pen by itself?

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

I''m working with a guy who has Apache 1.3 installed on his server, and it''s not an option to simply use lighttpd for a Rails application I''m helping him with. I''ve seen that Apache 2 apparently is crappy when it comes to fastcgi, but 1.3 isn''t so bad. I can then either just run my app straight in Apache, or I could proxy it through to lighttpd. Which