Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
We have about 5-6 different RTs setup on the same virtuals, some of them use
their own database, some of them share the same database
-Dimitry-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Dave Dennis
Sent: Friday, April 30, 2004 9:24 AM
To: RT Users
Subject: [rt-users] Two discrete instances of RT / same server
Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
Ooops…I mean on different virtuals but on the same server 
We have about 5-6 different RTs setup on the same virtuals, some of them use
their own database, some of them share the same database
-Dimitry-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Dave Dennis
Sent: Friday, April 30, 2004 9:24 AM
To: RT Users
Subject: [rt-users] Two discrete instances of RT / same server
Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
Dimitry,
Did that require an entire separate RT file hierarchy, which was
then referenced by the separate apache virtualhost ?
Ooops…I mean on different virtuals but on the same server
We have about 5-6 different RTs setup on the same virtuals, some of them use
their own database, some of them share the same database
-Dimitry
-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Dave Dennis
Sent: Friday, April 30, 2004 9:24 AM
To: RT Users
Subject: [rt-users] Two discrete instances of RT / same server
Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
±------------------------
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
Well, I’m not sure if it requires separate file hierarchy,
But the way we do that - yes, each time we install a brand new copy of RT
and then create a new virtual for itFrom: Dave Dennis [mailto:dmd@speakeasy.org]
Sent: Friday, April 30, 2004 9:36 AM
To: Dimitry Faynerman
Cc: ‘RT Users’
Subject: RE: [rt-users] Two discrete instances of RT / same server
Dimitry,
Did that require an entire separate RT file hierarchy, which was
then referenced by the separate apache virtualhost ?
Ooops…I mean on different virtuals but on the same server
We have about 5-6 different RTs setup on the same virtuals, some of them
use
their own database, some of them share the same database
-Dimitry
-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Dave Dennis
Sent: Friday, April 30, 2004 9:24 AM
To: RT Users
Subject: [rt-users] Two discrete instances of RT / same server
Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
±------------------------
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt
this spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
The easiest thing is to install RT multiple times, and
associated each rt install with a different fcgi process.
(And a different url or virtual host with each fcgi process.)
I have a somewhat fancier setup, in which I only need
a single RT install, but each fcgi process is passed
an environmental variable (specificed in the apache config)
that tells it where to look for the RT config file (and possible
local overlays).
This way, I can have multiple local configs (and gui changes,
etc) while having only one install of the RT core files.
Obviously these configs may or may not reference multiple mysql
databases. I did this mostly so I could run one apache server and
install RT once (with my own local mods that everyone must use) ,
yet give out different RT instances to different departments on
campus (each of which can be modified independently). As well, it
would be easy for me to keep a local config, and upgrade RT, just
mix and match.
The downside is that it requires a small patch to a couple files,
to read and act on the environment variable. I had submitted
this patch many months ago, but it didn’t seem to be of
general interest. Ask me offline if you’re interested in
more details.
bobg
The install I’d be doing this on is mod_perl .
Does that affect the outcome or limits ?
The easiest thing is to install RT multiple times, and
associated each rt install with a different fcgi process.
(And a different url or virtual host with each fcgi process.)
I have a somewhat fancier setup, in which I only need
a single RT install, but each fcgi process is passed
an environmental variable (specificed in the apache config)
that tells it where to look for the RT config file (and possible
local overlays).
This way, I can have multiple local configs (and gui changes,
etc) while having only one install of the RT core files.
Obviously these configs may or may not reference multiple mysql
databases. I did this mostly so I could run one apache server and
install RT once (with my own local mods that everyone must use) ,
yet give out different RT instances to different departments on
campus (each of which can be modified independently). As well, it
would be easy for me to keep a local config, and upgrade RT, just
mix and match.
The downside is that it requires a small patch to a couple files,
to read and act on the environment variable. I had submitted
this patch many months ago, but it didn’t seem to be of
general interest. Ask me offline if you’re interested in
more details.
bobg
Dear List,
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
Seems like the safest thing would be two separate mysql backends,
one running on a different port. Is it possible instead to
run both out of the same mysql, but rename ‘rt3’ to something else ?
if we had a completely separate {RT} home dir and separate etc,
separate Site_Config.pm, all referred by a second apache …
would things still break inside perl / mason somehow with shared
caches ?
Let me know if this would be feasable. If it is and nobody wrote a howto
yet I’d be willing to document steps taken and flush it out into a howto
that would be wiki-usable.
Kind regards,
±------------------------
The rt-users Archives
RT Developer and Administrator training is coming to LA, DC and Frankfurt this
spring and summer.
http://bestpractical.com/services/training.html
Sign up early, as class space is limited.
!DSPAM:40928d96265771371517052!
The install I’d be doing this on is mod_perl .
Does that affect the outcome or limits ?
Big time. The RT::… package is going to be loaded
by mod_perl just once. This will include RT::Config
which will have to be valid for all your instances.
If you stay with mod_perl, you have to run separate
instances of apache, since even different virtual hosts
will all share the same perl interpreter in mod_perl.
bobg
Dave Dennis wrote:
In the interest of brevity does anybody have experience with
standing up two apache each having an instance
of RT running on the same server ? We want to have a test-config
instance, as well as our existing running instance.
That’s not gonna work with mod_perl. You’ll want to use
FastCGI or separate apache instances.
Separate databases within the same MySQL instance is fine;
just set $DatabaseName appropriately in each RT_SiteConfig.