similar to: Lighttpd config...

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

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,

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

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

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''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''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, 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

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''m using lighty and fastcgi in my rails production environment. standard output appears to get swallowed up somewhere... it''s clearly not coming out of the development log. don''t know where to look for it. is this a byproduct of running in production mode? is there a way to turn this off? thanks, paul

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

Hi, While learning Ruby and Rails, I decided I just as well learn Linux along the way... It''s been fun, but I''m stuck at one of those exasperating moments... I hope someone can help me :) I installed Ruby 1.8.4 on Fedora Core 4, then Rails, then lighty, and then SCGI. I used yum to install lighty... and it already comes with mod_scgi. I created my first application in

I''m running lighttpd + fastcgi + rails Say that the lighttpd root directory is the rails application /public directory. I''m just curious. If theres a file in the document root with the same name as a controller, does the file get served first? How does that work? Does lighttpd check the root directory first to see if the file exists- If not, it calls dispatch.fcgi? I want to

Has anyone been able to get script/server to successfully use lighttpd on a Windows box? When I try to start the server I get: PROBLEM: Lighttpd is not available on your system (or not in your path) So then I add "C:\lighttpd\sbin" to the path for the console session, and it still fails with the same error. If anyone has some success with this I sure would like to know. Webrick

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

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

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

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

Hi, I''m new to Rails and was trying out the tutorial that they give on the apple website http://developer.apple.com/tools/rubyonrails.html I installed everything including lighttpd, and I got up to the point where I want to create my first record. When I hit the ''create'' button, lighttpd quits. If I have the server running as a foreground process I get this message

Hi, I have installed lighttpd1.4.10 on my debian server. The installation goes well and rails 1.0 do recognize lighty when I run script: ruby script\server. However, after the first request to lighty, lighty returned the right page, then shut itself down:( Did anybody had similar experience? Thanks! -Tony -- Posted via http://www.ruby-forum.com/.