A good article on setting up apache / mongrel is here: http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel
I've gone this route with my mac mini server (not under load yet, still setting up) and it was definitely easy. Just be sure you have apache 2 or greater - mod proxy balancer doesn't exist for version 1.
What else can I tell you? Mongrel is a no-brainer. It is stable as hell, and can serve your rails app all by itself if you don't expect heavy load or concurrent requests. From the performance tests I've seen, it is fairly easy to get a Mongrel setup to about 90% of the speed of a precisely-tuned FastCGI setup. Mongrel hasn't been around long enough to know what a precisely-tuned setup with it can do, but more and more people are switching to it. If you get comfortable with Mongrel + Apache, you'll have a skill set that ought to go far in the next few years with Rails.
Chris
On 10/22/06, Erik Hollensbe <[EMAIL PROTECTED]> wrote:
On Oct 22, 2006, at 8:48 PM, Dave Amos wrote:
> >My first advice would be to drop lighttpd and use mongrel plus pound
> >or apache. Is there a reason you want to use lighttpd? Fastcgi?
>
> I'm using lighttpd because I'm using Textdrive as a hosting
> provider and they seem to strongly recommend it. They even have a
> tutorial and everything, which I followed to the "T" and still had
> problems. I'd switch to Mongrel, but since I've never deployed an
> app before I kind of needed some serious handholding. What are the
> reasons for choosing mongrel or apache over lighttpd? Apache would
> be pretty convenient, actually, since I work for a website that
> uses apache, so I can ask one of the developers for help.
>
Dave,
I think it would be in your best interest to investigate a HTTPd for
its merits regardless of the stellar RoR support before settling with
something. Mongrel may be nice for getting a fast start at deploying
your static content, but as soon as you are in need of a PHP app,
sublime access features, or even static pages, you will find yourself
making the choice all over again.
Really, unless you have a very good reason to go with another daemon,
learning Apache will serve you (yuk yuk) better generally and is
worth learning even if you don't use that as your choice for the RoR
application. Apache also has a very solid user community which will
give you access to a lot of well-done user documentation along with
tips and modifications which can enhance your application with very
little additional work (mod_security, for instance.)
--
Erik Hollensbe
[EMAIL PROTECTED]
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
--
Chris Anderson
http://mfdz.com/jchris
_______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
