similar to: So...is lighttpd/fcgi on its way out, Apache/mongrel the up-and-comer?

Good evening (or afternoon or whatever it is where you are), Before I start setting it all up, I have a question about lighttpd and multiple rails apps. From what I have read, it is at the minute only possible to do multiple rails apps using subdomains: typo.mysite.com hieraki.mysite.com rforum.mysite.com etc, etc and not currently possible to do this: mysite.com/typo mysite.com/rforums

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

Hi all, I just updated lighttpd from 1.4.8 to 1.4.9 and it now refuses to start with the following error: 2006-01-24 23:12:24: (mod_fastcgi.c.989) execve failed for: public/ dispatch.fcgi No such file or directory 2006-01-24 23:12:24: (mod_fastcgi.c.1015) the fastcgi-backend public/ dispatch.fcgi failed to start: 2006-01-24 23:12:24: (mod_fastcgi.c.1019) child exited with status 2

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

Hi, I''m trying to setup up a rails deploy environment. I get an error when start lighty in production.log undefined method `downcase'' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/request.rb:17:in `method'' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:902:in `log_processing''

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

Hello all. Time for an all night installation campfire (no pun intended) story. I just helped a customer migrate from a single box to a 5 box system. 2 Lighty 2 FCGI 1 DB Everything went quite well. I scripted everything so it would be easy to add more boxes in the future. 3 scripts, one for each box type above. Then came time to get the site working. :-) Lighty came up easily. The DB came up

Hi guys, I''m here again with a problem. I have a rails app called brewed. It''s located /home/user/brewed. My lighttpd.conf is located at /home/user/lighty. When I execute lighty on port 80 with: /usr/local/sbin/lighttpd -f /home/user/lighty/lighttpd.conf rails seems to work fine. If I type www.mysite.com/main/index on my browser, the page comes out well. I have my files

I started what I thought was going to be a 30 minute project on the train this morning to write a little timetracker for myself. Amongst other things (don''t have a model called Task as it conflicts with Rake at the moment, don''t have a model called Action as it disappears in the hash when you submit a form :-), I had to use Webrick as Lighty complained about an unknown

I just got a new Debian Sarge server and followed the brainspl.at "Debian Lighttpd Rails Stack" tutorial. The only place I deviated was the version of Lighty. The page uses 1.4.7 and I spotted that 1.4.10 was available. I installed that and couldn''t get anywhere. Lighty died on first access from the test rails app, and even from a ultra basic static config. No log,

Hello everyone, I?ve been working with Ruby on Rails for about 2 months now and have really enjoyed the ease of use of it. I?m only been doing development on it so I?ve been using WeBrick. Recently, I have built a server running Debian Linux, with ruby 1.8.2, rails 1.0.0, lighty 1.4.3, and Mysql 5.0.18. I used WeBrick to generate a lighttpd.conf file for me, I changed the paths in the

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 all My lighty spawn 10 fcgi process, some times, one or two of them will eat all most 90% CPU, when i kill them, everything is ok. I want a script to auto kill these Big fcgi, could you give me some advise? regards -- Posted via http://www.ruby-forum.com/.

I''ve got switchtower set up, and it seems to work fine except for one problem: It doesn''t successfully restart lighttpd. I have the following task in my deploy.rb file: desc "Restart the web server" task :restart, :roles => :app do sudo "/usr/local/etc/rc.d/lighttpd.sh restart" end This is on a FreeBSD system, so it''s using the rc script to

Hello list, I''ve been developing a rails app using webrick as my server. I''m trying to change my server over to lighttpd as I am now attempting to deploy on a host that uses lighttpd. I had an older version of lighttpd installed and could never get it running correctly with my app. Preparing for deployment I decided to get lighty working and after poking around a bit I

I can''t figure out how to compile php with fcg enabled. I found a website which gives an example of how to write options in configure http://scoops.totallyrule.com/articles/2006/02/01/mysql5-ab-package-and-php5 So I wrote ./configure --prefix=/usr/local --program-suffix=5 --enable-fastcgi --enable-discard-path --enable-force-cgi-redirect --with-mysqli=/usr/local/mysql/bin/mysql_config

I just got a new Debian Sarge server and followed the brainspl.at "Debian Lighttpd Rails Stack" tutorial. The only place I deviated was the version of Lighty. The page uses 1.4.7 and I spotted that 1.4.10 was available. I installed that and couldn''t get anywhere. Lighty died on first access from the test rails app, and even from a ultra basic static config. No log, no

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

In case this helps anyone I recently finished setting up a Debian server closely following Ezra''s excellent guidance @ http://brainspl.at/rails_stack.html. I used newer libraries in some cases (and mysql 5.0) and everything worked great until the end when lighttpd wouldn''t start. I finally figured out that Lighty 1.4.9 has a problem working with rails out-of-the-box. See

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? --