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

Thomas Sibley trs at bestpractical.com
Tue Feb 15 13:37:55 EST 2011


On 15 Feb 2011 13:27, Nick Kartsioukas wrote:
> 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

The above line is most certainly incorrect.  The bin/rt that ships with
RT is the command-line utility, NOT the web interface handler.

Thomas



More information about the rt-users mailing list