Here’s the really quick theory behind how to do this. Sorry. I’m a bit rushed
right now But this should at least get you started.
Basically, you want to setup mod_proxypass on your RT server’s main RT instance.
Then, set up two seperate RT instances on two seperate apache servers running
on high ports on your RT host. On the high-port servers, configure each
RT instance to run in whatever root directory you want it to. Then configure
mod_proxypass to hand off requests.
If you have the time once you have it running, writing up a step-by-step howto
would be greatly appreciated.
-jesseOn Tue, Mar 27, 2001 at 02:00:46PM +0200, Christian Kurz wrote:
Hi Jesse and everyone else,
has anyone a good HowTo for running two instances of webrt with
different databases and different webinterfaces on one machine? This
would be very helpful and be needed by me. Thanks for any information.
autoconf is your friend until it mysteriously stops working, at which
point it is a snarling wolverine attached to your genitals by its teeth
(that said, it’s better than most of the alternatives) – Nathan Mehl
Right. which is why you want to be running a completely different instance
of Apache for each instance of RT. Of course, this will all be much easier
when we get speedycgi support working.
-jOn Fri, Mar 30, 2001 at 10:00:42AM +0200, Jonas Liljegren wrote:
Basically, you want to setup mod_proxypass on your RT server’s main RT
instance. Then, set up two seperate RT instances on two seperate
apache servers running on high ports on your RT host.
A problem with mod_perl is that the modules is shared between
sessions. (An that’s it’s strength to.) This has led me to insert the
version number in the module name just so that I can have two versions
of the same module on the same apache server.
It could be a lot of places to update the module names eith each
version change, but that can be automated in the make script.
Basically, you want to setup mod_proxypass on your RT server’s main RT instance.
Then, set up two seperate RT instances on two seperate apache servers running
on high ports on your RT host. On the high-port servers, configure each
So that means I add mod_proxypass as another module to the current
apache config and then create two virtual hosts like rt1.doma.in and
rt2.doma.in? Or do they need to be on a high port and if yes, why?
RT instance to run in whatever root directory you want it to. Then configure
What do you mean by root-directory? The dir, where all the html-stuff
should belong or where the databases are located on what exactly is
meant with root-dir?
mod_proxypass to hand off requests.
Hand off requests? What do you mean by that? I don’t know much about
Webservers or mod_proxypass, so some more explanation on this would be
helpful.
Also do I need to change all the email-aliases to use the different two
rt instances? If yes, I would then also need to change stripmime for one
instance to use the new dir, right?
If you have the time once you have it running, writing up a step-by-step howto
would be greatly appreciated.
Sorry, but I’m currently very busy and that’s why I already asked for a
Howto on this stuff.
Christian
Christian Kurz http://www.planNET.de
planNET Systems GmbH mailto:info@planNET.de
Schoenfeldstr. 8 Telefon: +49 721 66 36 0
D-76131 Karlsruhe Telefax: +49 721 66 36 199
Right. which is why you want to be running a completely different instance
of Apache for each instance of RT. Of course, this will all be much easier
when we get speedycgi support working.
Ahm, two different apache process? Hm, this can’t be handled via two
Virtual Hosts? Sounds like a system that you better set up once and then
never really touch again. Altough running two different apache process
will be a bit difficult for people who use the apache start script from
their distribution, which would require some hacking on them.
Christian
Christian Kurz http://www.planNET.de
planNET Systems GmbH mailto:info@planNET.de
Schoenfeldstr. 8 Telefon: +49 721 66 36 0
D-76131 Karlsruhe Telefax: +49 721 66 36 199
If you have the time once you have it running, writing up a step-by-step howto
would be greatly appreciated.
Sorry, but I’m currently very busy and that’s why I already asked for a
Howto on this stuff.
Welcome to the open source development process.
J.D. Falk “The Internet isn’t just a publishing medium or a
Product Manager medium for commerce, it’s a social medium.”
Mail Abuse Prevention System LLC – Howard Rheingold
Apache/mod_perl doesn’t actually really sandbox virtual hosts properly.
There’s not too much I can do about it. If someone else wants to look
at what it would take to get the speedycgi or fastcgi handlers into place,
that could also be a solution to this problem.On Tue, Apr 03, 2001 at 11:16:12AM +0200, Christian Kurz wrote:
On 01-03-30 Jesse wrote:
Right. which is why you want to be running a completely different instance
of Apache for each instance of RT. Of course, this will all be much easier
when we get speedycgi support working.
Ahm, two different apache process? Hm, this can’t be handled via two
Virtual Hosts? Sounds like a system that you better set up once and then
never really touch again. Altough running two different apache process
will be a bit difficult for people who use the apache start script from
their distribution, which would require some hacking on them.
Apache/mod_perl doesn’t actually really sandbox virtual hosts properly.
There’s not too much I can do about it. If someone else wants to look
at what it would take to get the speedycgi or fastcgi handlers into place,
that could also be a solution to this problem.
So I would either have to get the two instance of apache running and
then work around the other problems to get two instance of rt on one
host running? Hm, sounds like this is a lot more difficult then running
two copies of rt on two hosts. What would you suggest?
Christian
Christian Kurz http://www.planNET.de
planNET Systems GmbH mailto:info@planNET.de
Schoenfeldstr. 8 Telefon: +49 721 66 36 0
D-76131 Karlsruhe Telefax: +49 721 66 36 199
Apache/mod_perl doesn’t actually really sandbox virtual hosts properly.
There’s not too much I can do about it. If someone else wants to look
at what it would take to get the speedycgi or fastcgi handlers into place,
that could also be a solution to this problem.
So I would either have to get the two instance of apache running and
then work around the other problems to get two instance of rt on one
host running?
It’s really not that hard. It took me about 10 minutes the first time.
Besides running seperate apache instances, you just need to put your
two copies of RT in two seperate directories and point them at two different
databases on your mysql/postgresql/oracle server.
autoconf is your friend until it mysteriously stops working, at which
point it is a snarling wolverine attached to your genitals by its teeth
(that said, it’s better than most of the alternatives) – Nathan Mehl
Apache/mod_perl doesn’t actually really sandbox virtual hosts properly.
There’s not too much I can do about it. If someone else wants to look
at what it would take to get the speedycgi or fastcgi handlers into place,
that could also be a solution to this problem.
So I would either have to get the two instance of apache running and
then work around the other problems to get two instance of rt on one
host running?
It’s really not that hard. It took me about 10 minutes the first time.
Besides running seperate apache instances, you just need to put your
two copies of RT in two seperate directories and point them at two different
databases on your mysql/postgresql/oracle server.
Which is still difficult, since I use the debian package of rt
currently. So I would either have to create second package rt and use
other dirs in it, because the files are split over / (config in /etc,
binaries in /usr and databases in /var). Also that way I would have to
create a second database, name it different and make sure that the
second rt process only access that one. I think that’s a lot of work and
lot of points for failures, so either having two rt’s on two different
hosts or one rt and then use the acl’s would sound like a lot less work
then this.
Ciao
Christiah
Christian Kurz http://www.planNET.de
planNET Systems GmbH mailto:info@planNET.de
Schoenfeldstr. 8 Telefon: +49 721 66 36 0
D-76131 Karlsruhe Telefax: +49 721 66 36 199
Wait. are you talking about RT1? Or has soemone packaged RT2 for debian?
The .debs of RT1 most certainly only handle one install per box.
But, well, I know next to nothing about them. RT1 doesn’t need
the special apache config, because it’s not mod-perl based.
Anyway you slice it, installing two instances of RT on one box is
going to be more complex than one instance per box. The default config
just isn’t set up for multiple instances. Very few sites need it.
-jOn Wed, Apr 04, 2001 at 10:14:04AM +0200, Christian Kurz wrote:
On 01-04-04 Jesse wrote:
On Wed, Apr 04, 2001 at 10:03:25AM +0200, Christian Kurz wrote:
On 01-04-03 Jesse wrote:
Apache/mod_perl doesn’t actually really sandbox virtual hosts properly.
There’s not too much I can do about it. If someone else wants to look
at what it would take to get the speedycgi or fastcgi handlers into place,
that could also be a solution to this problem.
So I would either have to get the two instance of apache running and
then work around the other problems to get two instance of rt on one
host running?
It’s really not that hard. It took me about 10 minutes the first time.
Besides running seperate apache instances, you just need to put your
two copies of RT in two seperate directories and point them at two different
databases on your mysql/postgresql/oracle server.
Which is still difficult, since I use the debian package of rt
currently. So I would either have to create second package rt and use
other dirs in it, because the files are split over / (config in /etc,
binaries in /usr and databases in /var). Also that way I would have to
create a second database, name it different and make sure that the
second rt process only access that one. I think that’s a lot of work and
lot of points for failures, so either having two rt’s on two different
hosts or one rt and then use the acl’s would sound like a lot less work
then this.
Wait. are you talking about RT1? Or has soemone packaged RT2 for debian?
Yers, I talk about rt1 as rt2 is still not packaged and I think it will
first be package when it’s released.
The .debs of RT1 most certainly only handle one install per box.
Right and that’ s why it would be a lot of work to get two instance of
rt running on one debian box, if you don’t want to install .tar.gz on
it.
Anyway you slice it, installing two instances of RT on one box is
going to be more complex than one instance per box. The default config
just isn’t set up for multiple instances. Very few sites need it.
Thanks for all your comments.
Christian
Christian Kurz http://www.planNET.de
planNET Systems GmbH mailto:info@planNET.de
Schoenfeldstr. 8 Telefon: +49 721 66 36 0
D-76131 Karlsruhe Telefax: +49 721 66 36 199
But this should at least get you started.