[rt-users] Configuring Apache for RT

Dave Heistand dheistand at challiance.org
Wed Jul 18 07:53:23 EDT 2007


On Wed, 2007-07-18 at 09:00 +0200, Benjamin Weser wrote:
> 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.


> btw: Like Gobnat I didn't get FCGI to work on OpenSuSE10.2 but
> mod_perl works just fine.
> 
> To come back to topic: I didn't change much in the default apache
> configuration. Just added mod_perl and mod_php5 and set up some
> variables and my vhosts.conf and it worked well since then. 
> 
> I've spent much more time on configuring RT with all its rights etc
> and I bet I'm not done yet ;)
> 
> 
> 
> 
> jmoseley at corp.xanadoo.com schrieb: 
> > Choose the method you prefer, but I would at least try.  Other than Apache
> > and either mod_perl or some flavor of a FastCGI module, your only
> > dependencies are Perl modules.  Install the CPAN installer and use the
> > 'make fixdeps' option within the RT source code to install what it can.
> > Then install the rest of the rest of the modules via yum.  Finally, the few
> > that possibly don't install, get the source from CPAN and manually install
> > those last few Perl modules.  At this point, you're basically done.
> > 
> > You at least need to read the documentation on RT's website to know how to
> > configure Apache as well as the RT_SiteConfig.pm file.  Almost nothing you
> > install (Apache, Postfix, etc) via yum is going to work with the default
> > config files - you must read and understand the documentation and make the
> > changes necessary - this goes for RT as well.
> > 
> > Lastly, you should download the RT source, gunzip, untar, etc, read the
> > docs, do a './configure' and then do 'make testdeps' to see if you are
> > missing any dependencies that should have been installed during the yum
> > install of RT.  At least that will tell you if you are missing anything.
> > 
> > If you are unwilling to  do this, that's fine, but the help you receive on
> > this site is going to be limited.
> > 
> > 
> > James Moseley
> > 
> > 
> > 
> > 
> >                                                                            
> >              John Oliver                                                   
> >              <joliver at john-oli                                             
> >              ver.net>                                                   To 
> >              Sent by:                  rt-users at lists.bestpractical.com    
> >              rt-users-bounces@                                          cc 
> >              lists.bestpractic                                             
> >              al.com                                                Subject 
> >                                        Re: [rt-users] Configuring Apache   
> >                                        for RT                              
> >              07/17/2007 06:07                                              
> >              PM                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> > 
> > 
> > 
> > 
> > On Tue, Jul 17, 2007 at 04:36:26PM -0500, jmoseley at corp.xanadoo.com wrote:
> >   
> > > You state starting apache still fails...  I assume you did do the
> > > following:
> > > 
> > > yum install mod_fcgid
> > >     
> > 
> > Yes.
> > 
> >   
> > > Honestly, I would uninstall the RT3 RPM and install RT from source.
> > > Documentation is fairly straightforward.
> > >     
> > 
> > Not an option.  I wasted a week trying to resolve an endless string of
> > dependencies and was never able to get anywhere close to where I am now.
> > 
> > The fact that there are RPMs available in the yum repositories is more
> > likely to mean that someone has been able to make them work, rather than
> > someone is just a sadistic bastard.  I just wish they had bothered to
> > document the process.
> > 
> > --
> > ***********************************************************************
> > * John Oliver                             http://www.john-oliver.net/ *
> > *                                                                     *
> > ***********************************************************************
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> > 
> > Community help: http://wiki.bestpractical.com
> > Commercial support: sales at bestpractical.com
> > 
> > 
> > Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> > Buy a copy at http://rtbook.bestpractical.com
> > 
> > 
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> > 
> > Community help: http://wiki.bestpractical.com
> > Commercial support: sales at bestpractical.com
> > 
> > 
> > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> > Buy a copy at http://rtbook.bestpractical.com
> >   
> 
> 
> -- 
> OSP Dresden
> Benjamin Weser
> +49 351 49723 102
> weser at osp-dd.de
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com



More information about the rt-users mailing list