I currently have RedHat 7.3 on our RT 2 server. I plan to switch to a
new distro soon, and make the switch to RT3 at the same time.
I thought I might wait for the next Fedora release (2.6 kernel, etc.),
but thought I might ask which distro is the easiest to configure and
administer with RT.
I currently have RedHat 7.3 on our RT 2 server. I plan to switch to a
new distro soon, and make the switch to RT3 at the same time.
I thought I might wait for the next Fedora release (2.6 kernel, etc.),
but thought I might ask which distro is the easiest to configure and
administer with RT.
Opinions?
That distro which you know better.
If you read this list then you can see that people use it on different
systems: RH7,8,9, FreeBSD, Windows, Solaris, Debian, Fedora…
May be on systems where mp2 by default FastCGI is easy way.
If you want non ascii support you have to use perl5.8.3 which no one
provide so you should build your own perl package, RPM…
Some distro still use MySQL 3.x, but it’s better use 4.0.x
I’ve installed on RH 8, RH9, and Fedora Core 1. By FAR the easiest
was Fedora. Got it up and running in modperl2 with no issues, fastest
install (for me) on record…
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677 kfh@mqsoftware.com
I currently have RedHat 7.3 on our RT 2 server. I plan to switch to a
new distro soon, and make the switch to RT3 at the same time.
I thought I might wait for the next Fedora release (2.6 kernel, etc.),
but thought I might ask which distro is the easiest to configure and
administer with RT.
I currently have RedHat 7.3 on our RT 2 server. I plan to switch to a
new distro soon, and make the switch to RT3 at the same time.
I thought I might wait for the next Fedora release (2.6 kernel, etc.),
but thought I might ask which distro is the easiest to configure and
administer with RT.
On Debian sarge and up you can do a fresh OS install and then simply type:
apt-get install request-tracker3
apt will get all of the depends for you. After that cd to
/usr/share/doc/request-tracker3 and follow the directions. Had it up
and running in about 2 hours from empty hard drive to fully setup.
I’ve been considering my options for running rt3 on debian. I had come
to 2 conclusions.
Run stable and pin rt3 to unstable
Run unstable.
Option 1 is ugly. Option 2 was pretty much the way I was going to go.
I didn’t really consider using sarge, as security wise it’s in no mans
land and my RT3 will online.
I’m also gonna separate the (pg) db from the webserver/frontend. The db
will run on stable. See any issues with this?
thoughts?
jamieOn Thu, 2004-02-19 at 05:44, Sean Perry wrote:
On Debian sarge and up you can do a fresh OS install and then simply type:
apt-get install request-tracker3
apt will get all of the depends for you. After that cd to
/usr/share/doc/request-tracker3 and follow the directions. Had it up
and running in about 2 hours from empty hard drive to fully setup.
I’ve been considering my options for running rt3 on debian. I had come
to 2 conclusions.
Run stable and pin rt3 to unstable
Run unstable.
Option 1 is ugly. Option 2 was pretty much the way I was going to go.
I didn’t really consider using sarge, as security wise it’s in no mans
land and my RT3 will online.
I’m also gonna separate the (pg) db from the webserver/frontend. The db
will run on stable. See any issues with this?
I just installed Debian for the first time on a home box. I haven’t
even figured out yet how to get dselect to show me testing packages! :-\
But what do you mean about sarge being unsecure? Isn’t Sarge “testing”,
whereas “sid” is unstable? Wouldn’t that mean sid is less assured of
security than sarge?
I currently have RedHat 7.3 on our RT 2 server. I plan to switch to
a new distro soon, and make the switch to RT3 at the same time.
I thought I might wait for the next Fedora release (2.6 kernel,
etc.), but thought I might ask which distro is the easiest to
configure and administer with RT.
I use Debian with RT3. Specifically, I use Debian/stable with RT from
Debian/testing (and whatever dependencies that also requires from
testing). This is trivial to install: you start by installing stable,
then you add the testing apt sources to your /etc/apt/sources.list,
and then you run
and all the dependencies are taken care of for you.
The RT3 in testing is at 3.0.6, which is a little behind unstable
(3.0.8), but the lag usually isn’t more than a few weeks, and I
prefer not to run other packages from unstable.
I didn’t really consider using sarge, as security wise it’s in no
mans land and my RT3 will online.
But what do you mean about sarge being unsecure? Isn’t Sarge
“testing”, whereas “sid” is unstable? Wouldn’t that mean sid is less
assured of security than sarge?
Only stable recieves security updates. For unstable, you wait till the
maintainer releases a new package (usually quite promptly), though I
don’t think it usually get’s pushed into testing very fast.
I’m also gonna separate the (pg) db from the webserver/frontend. The db
will run on stable. See any issues with this?
well, pg on stable is 7.2.1, and on unstable it’s 7.4.1. If you need
performance, maybe running pg on unstable is the better thing to do.
For me, it feels much cleaner and faster, but YMMV.
I’ve been considering my options for running rt3 on debian. I had come
to 2 conclusions.
Run stable and pin rt3 to unstable
Run unstable.
Option 1 is ugly. Option 2 was pretty much the way I was going to go.
RT 3 runs best with Perl 5.8.3, which pretty much rules out using Debian
stable.
Perl 5.8.3 should be in Sarge (testing). Sarge is on the verge of
becoming stable, and with luck will be there by summer. I would suggest
subscribing to the Debian Security mailing list, and running Sarge.
Then, when it goes stable, you are set.
Fortunately, I’m not the initial poster.
Your advice is somewhat misguided. If I used testing, I’d have to take
of security updates myself. Among other things, this requires that I’d
be able to apply security patches to Debian packages on my own…
Damn “reply” instead of “reply-all”.
Yes, you would have to watch security updates yourself, but soon (I
hope!) Sarge will be stable, and then it will be getting nice security
updates. But you know, I still watch for security updates for my Stable
machines.
So, if not a pure Sarge, what about a Woody/Sarge mix? Install Woody,
then add the testing lines in source.list and apt-get the packages
needed for RT 3. Do a dist-upgrade when Sarge moves to Stable.