Integrating RT 2.x into an existing Virtual Host

RT Users
1

Not sure if anyone has tackled this one, but there was some resistance
here to use yet another host name for an administrative web site here.
So, I managed to integrate the RT2.x installation into our current
administrative server by making some modifications to the current
Virtual Host installation, and I thought I would pass the configuration on.

Essentially, you have to specifiy Location directives for each of the
possible URL requests for RT2.

My resulting Virtual Hosts directive now includes:

PerlModule Apache::DBI
PerlFreshRestart On
PerlRequire /usr/rt2/bin/webmux.pl
Alias /rt2/ /usr/rt2/WebRT/html/
<Location /rt2/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /Ticket/ /usr/rt2/WebRT/html/Ticket/
<Location /Ticket/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /Admin/ /usr/rt2/WebRT/html/Admin/
<Location /Admin/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /Elements/ /usr/rt2/WebRT/html/Elements/
<Location /Elements/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /NoAuth/ /usr/rt2/WebRT/html/NoAuth/
<Location /NoAuth/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /Search/ /usr/rt2/WebRT/html/Search/
<Location /Search/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /SelfService/ /usr/rt2/WebRT/html/SelfService/
<Location /SelfService/>
SetHandler perl-script
PerlHandler RT::Mason

Alias /User/ /usr/rt2/WebRT/html/User/
<Location /User/>
SetHandler perl-script
PerlHandler RT::Mason

And everything just works if you go to
http://virtualhost.mydomain.com/rt2/. :slight_smile:

-Rich

Richard West mailto:rwest@wesmo.com Got TV?
Wesmo Computer Services http://www.wesmo.com Get your .TV!
Full Domain Registration Services
For As Little As $14.95/yr! .BIZ & .INFO Registrations Available NOW!

2

And everything just works if you go to

http://virtualhost.mydomain.com/rt2/. :slight_smile:

Every part of RT should be under /rt2/, so it should be /rt2/Ticket/ and
not /Ticket/. That way, you would only need one Location directive with
a SetHandler/PerlHandler statement.

The whole story makes me think you missed the $WebPath setting in
config.pm. If you missed that setting (and left it blank), RT links to
your server root (“/”) and causes the problems you describe. You just
solved the symptoms with an extraordinary Apache config, but the real
problem lies in your RT configuration.

Take a look at the documentation on
http://www.helgrim.com/rtdocs/installation.html#27
Paragraph 7.2.1 describes the situation where RT lives with other
content on a single webserver.

Martin

Martin Schapendonk, martin@schapendonk.org, Phone: +31 (0)6 55770237
Student Information Systems and Management at Tilburg University

3

:slight_smile: Found it… Jesse pointed out my oversight right away… :slight_smile:

-Rich

Martin Schapendonk wrote:>On Mon, 8 Oct 2001, Rich West wrote:

And everything just works if you go to

http://virtualhost.mydomain.com/rt2/. :slight_smile:

Every part of RT should be under /rt2/, so it should be /rt2/Ticket/ and
not /Ticket/. That way, you would only need one Location directive with
a SetHandler/PerlHandler statement.

The whole story makes me think you missed the $WebPath setting in
config.pm. If you missed that setting (and left it blank), RT links to
your server root (“/”) and causes the problems you describe. You just
solved the symptoms with an extraordinary Apache config, but the real
problem lies in your RT configuration.

Take a look at the documentation on
http://www.helgrim.com/rtdocs/installation.html#27
Paragraph 7.2.1 describes the situation where RT lives with other
content on a single webserver.

Martin