How would one set up two instances of RT3 on one RedHat 7.3 box with mod_perl compiled into Apache? The first instance is alive and well, but my company is starting up a second customer base that will require different configuration…
I picture two separate virutal domains on Apache, one for each interface. The configure file would point to non-default file locations and to a separate MySQL database. Once the second instance is installed, the configuration file in RTx/etc would use different database names, RT users, URLs, etc. More aliases for the new instance would go into the aliases file.
What are the gotchas? Any pointers would be appreciated.
This one time, at band camp, Joseph McCarty wrote:
How would one set up two instances of RT3 on one RedHat 7.3 box with mod_perl compiled into Apache? The first instance is alive and well, but my company is starting up a second customer base that will require different configuration…
I picture two separate virutal domains on Apache, one for each interface. The configure file would point to non-default file locations and to a separate MySQL database. Once the second instance is installed, the configuration file in RTx/etc would use different database names, RT users, URLs, etc. More aliases for the new instance would go into the aliases file.
What are the gotchas? Any pointers would be appreciated.
You can’t do it with mod_perl because of the way mod_perl loads the entire
instance and thus you need at least one of them running from fastcgi or
speedycgi.
JW> You can’t do it with mod_perl because of the way mod_perl loads the entire
JW> instance and thus you need at least one of them running from fastcgi or
JW> speedycgi.
sure you can. you just can’t have them both bind to the same IP/port
combination. If you have multiple IP addresses, just have each
instance of apache bind to just one of them. If you have one IP, then
you can have them each bind to a different port number, and have a
front-end listen on port 80 doing name-based virtual hosts and pass
the connections off via mod_proxy to the proper back end via the port
number.
How would one set up two instances of RT3 on one RedHat 7.3 box with
mod_perl compiled into Apache? The first instance is alive and
well, but my company is starting up a second customer base that will
require different configuration…
I picture two separate virutal domains on Apache, one for each
interface. The configure file would point to non-default file
locations and to a separate MySQL database. Once the second
instance is installed, the configuration file in RTx/etc would use
different database names, RT users, URLs, etc. More aliases for the
new instance would go into the aliases file.
What are the gotchas? Any pointers would be appreciated.
You can’t do it with mod_perl because of the way mod_perl loads the entire
instance and thus you need at least one of them running from fastcgi or
speedycgi.
You can also run seperate apaches (on different ports) if you need
everything to appear to be on ports 80 and 443, you can have one
apache proxy to the other, or have a thrid that proxies to those 2.
Instead of having a VirtualHost (and corresponding DNS entry to point to
that host), can we configure Apache with some alternative ways of getting
there.
But that’s obviously not enough - if you try to use anything of RT from
that page, it will just attempt to redirect per the suggested VirtualHost
entry which points DocumentRoot to /usr/local/rt3/html.
JW> You can’t do it with mod_perl because of the way mod_perl loads the entire
JW> instance and thus you need at least one of them running from fastcgi or
JW> speedycgi.
sure you can. you just can’t have them both bind to the same IP/port
combination. If you have multiple IP addresses, just have each
instance of apache bind to just one of them. If you have one IP, then
you can have them each bind to a different port number, and have a
front-end listen on port 80 doing name-based virtual hosts and pass
the connections off via mod_proxy to the proper back end via the port
number.
Yeah, so you need two apaches, you can’t do it in a single apache instance.
Instead of having a VirtualHost (and corresponding DNS entry to point to
that host), can we configure Apache with some alternative ways of getting
there.
But that’s obviously not enough - if you try to use anything of RT from
that page, it will just attempt to redirect per the suggested VirtualHost
entry which points DocumentRoot to /usr/local/rt3/html.
I think you are missing /share/html at the end of your Alias line.
Also theres doc for this at http://www.fsck.com/rtfm/article.html?id=2.
check ‘Configure the web interface sub-section’