Configuring Apache for RT

First I had a lot of trouble installing RT from source too. (On
OpenSuSE10.2). It worked for me like the Gobnat’s “diary” at
http://wiki.bestpractical.com/view/OpenSuSE101InstallGuide. That
happened to me as I tried to evaluate RT on my working computer. Later
I installed it again on a server in our LAN without any possibility
for internet and the usage of yast or cpan or whatever. Was a little
bit annoying with all those perl dependencies, I bet I downloaded at
least 50 and installed them seperately. I needed a whole morning until
I was done with perl. On the other hand I just took mandatory packages
and absolutely no optional. Seems this saved me a lot of trouble which
happened like in the above mentioned “diary”.

So my recommendation is to try to install RT from source and do not
install any optional packages from perl.

This is similar to what I did as I’ve always been worried about
installing perl modules using perl -MCPAN -e shell due to potential file
conflicts. I built all the perl modules RT requires as RPMS for CentOS
using cpanflute2. There were a few RPMS that had issues, I think the
DBI search builder module requires oracle unless you do some things to
force it to not check for oracle. Off the bestpratical site I found a
link to a repo that had older SRPMS and used them for a starting point
for modules like that.

At any rate, after spending some time getting those modules built it is
easy to get RT and RTFM to install. I install RT/RTFM from source as it
seems easier to upgrade and replicate RT to another server. Now when I
want to upgrade or test an upgrade I just build a new CentOS server,
copy the perl modules to the new server and do a

rpm -ivh perl-*

and then copy the database and rsync /opt/rt3 to the new server.

RT does a nice job of checking for the perl modules it needs, so usually
there are only one or two modules that need to be updated. I either use
the SPEC file from the old module to build the new rpm or just use
cpanflute to build a new rpm.

Once I’m ready to move the new release into production I’ll do a fresh
install of the OS and perl modules and then a clean install of RT/RTFM
from source after migrating the database.

I plan to look into the fedora based RPMS that people mentioned earlier
for the perl modules as I’d rather use ‘official’ SRPMs and rebuild them
for my specific OS. I will still install RT/RTFM from source though as
it makes it easier to stay current.

I’ve just been trying to set up RT on Fedora 7 and hit the same problem
reported in the list.

I’ve found that if I make my document root /usr/share/rt3/html then RT
works.

If not - i.e., if I leave my root at /var/www/html and put in a link to
/usr/share/rt3/html, I get the error
message about mod_perl, etc.

Any ideas?

Paul.

This email message may contain privileged/confidential information and/or
copyright material. It is intended only for the use of the person(s) to whom
it is addressed and any unauthorised use may be unlawful. If you receive this
email by mistake, please advise the sender immediately by using the reply
facility in your email software and delete the material from your computer.

The material contained in this message does not constitute a binding
contract with any company within the MTL Instruments Group plc. Opinions,
conclusions and other information in this email that do not relate to the official
business of this organisation shall be understood as neither given nor endorsed
by it. Registered in England No. 1871978, VAT Reg. No 449343040,
MTL Instruments Ltd, Power Court, Luton, LU1 3JJ