Thanks for clarification.
-----Original Message-----
From: Curt Hibbs [mailto:curt.hibbs at gmail.com]
Sent: Thursday, January 11, 2007 5:06 PM
To: Leonid Raiz
Cc: instantrails-users at rubyforge.org
Subject: Re: [Instantrails-users] Staring application with Mongrel
withoutshutting down IIS
I think you're working with an incorrect mental model of how things are
working.
Mongrel is a web server (written in Ruby) that has been configured to serve
up "myapp" on port 3004. Once you started up myapp via Mongrel, you can
browse to it using http://myapp:3004 or even http://127.0.0.1:3004
In fact, when you are developing a Rails app, this is generally what you do
(leaving out Apache entirely). Even in production, if you only needed to
serve up a single Rails-based web site, you could just configure Mongrel to
serve the Rails app on port 80.
Apache comes in to play when you want to test in a production-like
environment where you have multiple web apps running via Mongrel (each on
separate port) and then you use Apache handle requests on port 80 and proxy
those requests over to the various instances of Mongrel depending on the
URL.
Curt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/instantrails-users/attachments/20070111/d086dceb/attachment.html