[rt-users] Making New RT Install accessible from example.com/rt when example.com/ hosts another website

[Mark Lewis]

Nick,

Thanks for the reply.

I'm closer! I now get 403 Forbidden when I go to www.example.com/rt instead of a 404.

I corrected my RT_SiteConfig.pm file per your instruction, that makes sense to me now.

I removed all the virtual host crap, and added:

------------------------------------------------
<Directory "/var/www/htdocs/base/bin/rt">
        Options FollowSymLinks
        AllowOverride None
</Directory>

ScriptAlias /rt /var/www/htdocs/base/bin/rt
------------------------------------------------

So, now its 403'ing. I will continue to tinker but if you see something noticeably off here, your input is MUCH appreciated!!


Thanks again!



--
Mark Lewis
Intellifuel Systems, Inc.
1431 Chaffee Dr. Suite 6 | Titusville, FL 32780
office: 321-264-8707 x 241 | fax: 321-264-8709
markl at intellifuel.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.

Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.

If you received this communication in error, please contact the sender and delete the material as well as all copies.

-----Original Message-----
From: Nick Kartsioukas [mailto:change+lists.rt at nightwind.net]
Sent: Tuesday, February 15, 2011 1:27 PM
To: Mark Lewis; rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Making New RT Install accessible from example.com/rt when example.com/ hosts another website

On Tue, 15 Feb 2011 12:03 -0500, "Mark Lewis" <markl at intellifuel.com>
wrote:
> RT was installed to: /var/www/htdocs/base/bin/rt/
> The other website hosted here lives at: /var/www/htdocs/
> I need RT accessible at: http://www.example.com/rt

In your RT_SiteConfig.pm:
Set($WebPath, "/rt");
Set($WebBaseURL, "http://www.example.com");

In your Apache config, you wouldn't set up a new VirtualHost directive,
you would put the RT config within the existing VirtualHost directive
for example.com.  Something like this (check your docs and other
examples to confirm, this likely won't be 100% correct):
<Directory "/var/www/htdocs/base/bin/rt"
 Options FollowSymLinks ExecCGI
 AllowOverride None
</Directory>
ScriptAlias /rt /var/www/htdocs/base/bin/rt/bin/rt  <- the actual rt
perl executable