<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
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
<a class="moz-txt-link-freetext" href="http://wiki.bestpractical.com/view/OpenSuSE101InstallGuide">http://wiki.bestpractical.com/view/OpenSuSE101InstallGuide</a>. 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".<br>
<br>
<b>So my recommendation is to try to install RT from source and do not
install any optional packages from perl.</b><br>
<br>
btw: Like Gobnat I didn't get FCGI to work on OpenSuSE10.2 but mod_perl
works just fine.<br>
<br>
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. <br>
<br>
I've spent much more time on configuring RT with all its rights etc and
I bet I'm not done yet ;)<br>
<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jmoseley@corp.xanadoo.com">jmoseley@corp.xanadoo.com</a> schrieb:
<blockquote
cite="midOF6253FA24.24AB5594-ON8625731B.00814951-8625731B.00824D1A@pgtv.com"
type="cite">
<pre wrap="">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
<a class="moz-txt-link-rfc2396E" href="mailto:joliver@john-oliver.net"><joliver@john-oli
ver.net></a> To
Sent by: <a class="moz-txt-link-abbreviated" href="mailto:rt-users@lists.bestpractical.com">rt-users@lists.bestpractical.com</a>
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, <a class="moz-txt-link-abbreviated" href="mailto:jmoseley@corp.xanadoo.com">jmoseley@corp.xanadoo.com</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">You state starting apache still fails... I assume you did do the
following:
yum install mod_fcgid
</pre>
</blockquote>
<pre wrap=""><!---->
Yes.
</pre>
<blockquote type="cite">
<pre wrap="">Honestly, I would uninstall the RT3 RPM and install RT from source.
Documentation is fairly straightforward.
</pre>
</blockquote>
<pre wrap=""><!---->
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 <a class="moz-txt-link-freetext" href="http://www.john-oliver.net/">http://www.john-oliver.net/</a> *
* *
***********************************************************************
_______________________________________________
<a class="moz-txt-link-freetext" href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a>
Community help: <a class="moz-txt-link-freetext" href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</a>
Commercial support: <a class="moz-txt-link-abbreviated" href="mailto:sales@bestpractical.com">sales@bestpractical.com</a>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at <a class="moz-txt-link-freetext" href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</a>
_______________________________________________
<a class="moz-txt-link-freetext" href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a>
Community help: <a class="moz-txt-link-freetext" href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</a>
Commercial support: <a class="moz-txt-link-abbreviated" href="mailto:sales@bestpractical.com">sales@bestpractical.com</a>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at <a class="moz-txt-link-freetext" href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
OSP Dresden
Benjamin Weser
+49 351 49723 102
<a class="moz-txt-link-abbreviated" href="mailto:weser@osp-dd.de">weser@osp-dd.de</a></pre>
</body>
</html>