[rt-users] RT3 vs. Default Apache Page

[Josh Boon]

Post to the list.  My first was rejected due to an error on my part.

---------- Forwarded message ----------
From: Josh Boon <qwert2332 at gmail.com>
Date: Sun, Apr 11, 2010 at 16:17
Subject: Re: [rt-users] RT3 vs. Default Apache Page
To: Joseph Spenner <joseph85750 at yahoo.com>
Cc: rt-users at lists.bestpractical.com


Joesph,

Yep you can change your config to look like this:


NameVirtualHost  *

<VirtualHost *>
    ServerName *

    DocumentRoot /opt/rt3/share/html
    AddDefaultCharset UTF-8

    PerlModule Apache::DBI
    PerlRequire /opt/rt3/bin/webmux.pl

    <Location />
        SetHandler perl-script
        PerlHandler RT::Mason
    </Location>
</VirtualHost>

If the server ended up needing to run something else using the same apache
instance you can add a second host still by following the configuration
examples at http://httpd.apache.org/docs/1.3/vhosts/name-based.html.
Remember that all generic requests will go to the first vhost found and
specific ones will go to the vhost specified.

All the best,
Josh

On Sun, Apr 11, 2010 at 13:54, Joseph Spenner <joseph85750 at yahoo.com> wrote:

> My RT3 works great, but I have an apache config question regarding the
> default page.
> I often want to connect into my RT via SSH.  I do this by building an ssh
> port forward-- something like:
>
> ssh -l joseph -L 10080:10.4.5.6:80 ip.of.external.system
>
> Then if I http://127.0.0.1:10080 I would like to access RT.  However, upon
> doing so, I get the default apache page.  My apache config has:
>
> ===
> <VirtualHost 10.4.5.6>
>     ServerName 10.4.5.6
>     DocumentRoot /opt/rt3/share/html
>     AddDefaultCharset UTF-8
>
>     PerlModule Apache::DBI
>     PerlRequire /opt/rt3/bin/webmux.pl
>
>     <Location />
>         SetHandler perl-script
>         PerlHandler RT::Mason
>     </Location>
> </VirtualHost>
> ===
>
> I believe the problem is due to the     ServerName 10.4.5.6.
> For testing, if I make it this:  ServerName 127.0.0.1:10080
> RT is accessible through the port forward.  But this config will break it
> for the internal people.
>
> This web server doesn't need to serve any other content.  Can I simply
> remove the VirtualHost tags and modify the config such that no matter how
> this web server is reached it will serve RT?
>
> Thanks!
>
>
> If life gives you lemons, keep them-- because hey.. free lemons.
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20100411/65604461/attachment.htm>