RHEL4 does come with MySQL 4 client and server, and you can
install the server this time. As you said, RHEL3 did not
allow for the server to be installed by default. If I
remember correctly, mysql-server was on one of the extras
disks, but I could be wrong there.
RHEL3 comes with MySQL 3. It was included in my distribution from
Rackspace, and I don’t think they mess w/ things very much. I
uninstalled it and installed MySQL 4.1 from the MySQL-provided binary
RPMs.
Scenario 1: Using RPMS
Actually I was wrong – I apparently got lazy and used the ActivePerl
5.8 RPM distribution, installing it in /opt/pkg. THEN I added Perl
modules from the RT configure script. This has worked fine.
Thoughts???
Also, someone commented that I might have an easier go of it
if I used FastCGI rather than modperl. I’m curious why this is?
This worked just fine for me w/ Apache2:
Alias /rt “/opt/rt3/share/html”
PerlModule Apache::DBI
PerlRequire /opt/rt3/bin/webmux.pl
<Directory /opt/rt3/share/html>
AllowOverride All
Options ExecCGI FollowSymLinks
- re-install (maybe) RHEL4 or just remove all the perl
Packages and build my own perl from sources
- Use CPAN to get modperl and all the modules I'll need
- Install RT 3.0.12
- Do some testing
- Upgrade to 3.4.x
I would strongly encourage this route. Keeping your own perl makes
upgrades much simpler, since rpm and cpan aren’t stepping on
eachother.
There’s no reason you have to remove the rhel4 perl. it lives over in
/usr, your perl lives in /opt. Just make sure you build RT with the
right one.
I find fastcgi faster and less error prone than mod-perl.
We have RT 3.0.12 install running on a windows system that’s relied upon.
IT wants to use RT for internal ticketing, so I’m going to combine the two
on one server class Linux box. So, I’ll need to import the 3.0.12 data from
the windows box on 3.0.12 and then upgrade. At least that’s the process
I’ve seen and read in the docs.
- re-install (maybe) RHEL4 or just remove all the perl
Packages and build my own perl from sources
- Use CPAN to get modperl and all the modules I'll need
- Install RT 3.0.12
- Do some testing
- Upgrade to 3.4.x
I suspect that using CPAN, modulo the current problem with DBD::Pg,
which likely won’t affect you if you choose My, will be a better way to
keep things in sync.
Also, someone commented that I might have an easier go of it if
I used FastCGI rather than modperl. I’m curious why this is?
Hadn’t you said you preferred to use A2/MP2? That hasn’t been
considered quite ready for prime time, to date… though I’m using it,
and it seems to be working ok for me.
Cheers,
– jra
Jay R. Ashworth jra@baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
If you can read this... thank a system adminstrator. Or two. --me
We have RT 3.0.12 install running on a windows system that’s relied upon.
IT wants to use RT for internal ticketing, so I’m going to combine the two
on one server class Linux box. So, I’ll need to import the 3.0.12 data from
the windows box on 3.0.12 and then upgrade. At least that’s the process
I’ve seen and read in the docs.
Ah.
I’d been wondering about that too.
Cheers,
– jra
Jay R. Ashworth jra@baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
If you can read this... thank a system adminstrator. Or two. --me
