Rails - Aug 2006 - deploying with mongrel (how to avoid using the port number)

It looks like it should be possible using an .htaccess file and the 
ProxyPass commands, but everything I''ve attempted so far has led me to
a
500 internal server error.

-- 
Posted via http://www.ruby-forum.com/.

Using fcgi it was possible to avoid having to specify the port number 
when accessing a rails app by remapping the sub-domain to point to the 
''public'' directory.  Is this still possible when using
mongrel?

-- 
Posted via http://www.ruby-forum.com/.

On 8/10/06, Ryan Mohr <ryan.mohr@gmail.com> wrote:
> Using fcgi it was possible to avoid having to specify the port number
> when accessing a rails app by remapping the sub-domain to point to the
> ''public'' directory.  Is this still possible when using
mongrel?
Whatever server you were running fastcgi under had to have a port
number defined.  Mongrel is an http server, and has to define the port
it listens on.  You can''t tell a server to ''run on all
ports''.

What problem is it you are trying to solve?

snacktime wrote:
> On 8/10/06, Ryan Mohr <ryan.mohr@gmail.com> wrote:
>> Using fcgi it was possible to avoid having to specify the port number
>> when accessing a rails app by remapping the sub-domain to point to the
>> ''public'' directory.  Is this still possible when
using mongrel?
> 
> Whatever server you were running fastcgi under had to have a port
> number defined.  Mongrel is an http server, and has to define the port
> it listens on.  You can''t tell a server to ''run on all
ports''.
> 
> What problem is it you are trying to solve?
Yes, the server has to run on a port, but with fcgi it was easy to just 
point the root url into the public directory to avoid the visitors ever 
needing to specify the port number.  The same does not appear to be as 
easy with mongrel.  ProxyPass does look like it would work, but my host 
(dreamhost) has disabled it.  Is there an easy method I''m overlooking?

-- 
Posted via http://www.ruby-forum.com/.