osdir.com
mailing list archive

Subject: Mongrel, sit!, good god! -- said Rails core. - msg#00142

List: lang.ruby.mongrel.general

Date: Prev Next Index Thread: Prev Next Index
Oh well, needed a good subject, sounds funny enough?

http://dev.rubyonrails.org/ticket/5475

Add "automatic" mongrel support to script/server

Status: closed, commited in rev #4486.

That is good news, right?

Ok, back to work, enoguh relax for me ;-)

--
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Bare naked server

Thanks, Zed, for mongrel :!) I've been on TextDrive for some time running my sites behind apache w/lighttpd. Once it got running it was cool enough. When it ran. And there was still the webmin dance and all. So I decided to set things up on my little dedicated redhat server - since I'd had so much success locally w/mongrel. Fast. Simple. It has been great and I managed to move all my sites into it and off TD. Smooth as glass thus far. So, I decided I did not need no stinking apache ;-) Zed said : >Mongrel was >specifically designed to be run as a non-privileged user on a higher >port in order to avoid these kinds of things. In reality if you're >running Mongrel you should put it behind another web server and let that >web server defend port 80 for you. Doh. My understanding was that running a server in front of apache was primarily because apache(other) was good/better at serving static files. But since my performance thus far has been good(much faster now than apache/mod_ruby) I've not sweat it.(thinking in the future I'd serve images from another server if nec.) Are there other reasons, besides load, that I might be stupid for leaving mongrel running bare on port 80? Are the mongrel police going to come get me? I did have one interesting error that was being thrown because I was unable to grab the host name for a request. For some reason http:///w00tw00t.at.ISC.SANS.DFind: was landing on my port. I'm sending :status => 404 now(rather than dieing, which is caught by exception notifier) Are these the type of things I should be worried about? http://www.atlink.it/~conti/2006/03/04/w00tw00tatiscsansdfind-update/

Next Message by Date: click to view message preview

Re: Bare naked server

Multiple incoming requests? Mongrel (or, more specifically, Rails itself) can only handle a single request at a time, right? - James Moore

Previous Message by Thread: click to view message preview

Bare naked server

Thanks, Zed, for mongrel :!) I've been on TextDrive for some time running my sites behind apache w/lighttpd. Once it got running it was cool enough. When it ran. And there was still the webmin dance and all. So I decided to set things up on my little dedicated redhat server - since I'd had so much success locally w/mongrel. Fast. Simple. It has been great and I managed to move all my sites into it and off TD. Smooth as glass thus far. So, I decided I did not need no stinking apache ;-) Zed said : >Mongrel was >specifically designed to be run as a non-privileged user on a higher >port in order to avoid these kinds of things. In reality if you're >running Mongrel you should put it behind another web server and let that >web server defend port 80 for you. Doh. My understanding was that running a server in front of apache was primarily because apache(other) was good/better at serving static files. But since my performance thus far has been good(much faster now than apache/mod_ruby) I've not sweat it.(thinking in the future I'd serve images from another server if nec.) Are there other reasons, besides load, that I might be stupid for leaving mongrel running bare on port 80? Are the mongrel police going to come get me? I did have one interesting error that was being thrown because I was unable to grab the host name for a request. For some reason http:///w00tw00t.at.ISC.SANS.DFind: was landing on my port. I'm sending :status => 404 now(rather than dieing, which is caught by exception notifier) Are these the type of things I should be worried about? http://www.atlink.it/~conti/2006/03/04/w00tw00tatiscsansdfind-update/

Next Message by Thread: click to view message preview

Re: Mongrel, sit!, good god! -- said Rails core.

On Tue, 2006-06-27 at 14:02 -0300, Luis Lavena wrote: > Oh well, needed a good subject, sounds funny enough? > > http://dev.rubyonrails.org/ticket/5475 > > Add "automatic" mongrel support to script/server > > Status: closed, commited in rev #4486. > > That is good news, right? > > Ok, back to work, enoguh relax for me ;-) > Yeah man, it's very cool. If people have mongrel installed then they can do script/server mongrel and it'll start right up. Should make lots of folks happy. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by