[rt-users] Running RT on one system with the backend on another

[Matthew Watson]

This is pretty much all you have to do, just change the $DatabaseHost
from "localhost" to the name of your database machine.

The front end machine obviously needs all the RT libraries, but the
database host needs none of these, just needs to accept connections from
your frontend.

Regards
Matt.


> 
> I am running this in production mode, with a front end on one server
and
> the
> backend on two clustered sql servers. All I really did was point rt to
the
> db on the remote server.
> 
> 
> On 3/7/05 3:12 PM, "Vicki Stanfield" <vicki at progeny.com> wrote:
> 
> > Is there explicit documentation somewhere about how to run RT from
one
> > system and have the database on another system? That is the setup I
have
> > inherited, so I have the basic idea, but I'd really like to see it
> > documented before something happens and I have to fix it.
> >
> > Vicki
> >
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> >
> > RT Administrator and Developer training is coming to your town soon!
> (Boston,
> > San Francisco, Austin, Sydney) Contact training at bestpractical.com
for
> details.
> >
> > Be sure to check out the RT Wiki at http://wiki.bestpractical.com
> >
> 
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> RT Administrator and Developer training is coming to your town soon!
> (Boston, San Francisco, Austin, Sydney) Contact
training at bestpractical.com
> for details.
> 
> Be sure to check out the RT Wiki at http://wiki.bestpractical.com

This email and any files transmitted with it are confidential and intended solely for the 
use of the individual or entity to whom they are addressed. Please notify the sender 
immediately by email if you have received this email by mistake and delete this email 
from your system. Please note that any views or opinions presented in this email are solely
 those of the author and do not necessarily represent those of the organisation. 
Finally, the recipient should check this email and any attachments for the presence of 
viruses. The organisation accepts no liability for any damage caused by any virus 
transmitted by this email.