Martin,
I just have a completely seperate installation of each (i.e.
/usr/local/openca1, /var/www/html/openca1, /usr/local/openca2,
/var/www/html/openca2) each with their own database. This is also how I
separate the CA and RA (when I am testing on a single box).
Apart from the multiple instances of the modules and libraries I can't
really see a problem with this method.
yes, assuming the OpenCA instances were installed using
configure && make install the paths are correct for each individual
install.
Yes.
But for production deployment (at least in our case) it is
desirable to have the system installed from a package (RPM in my
case).
The packages install in the directory determined at package build time,
making your approach harder.
I see, yes that would be a problem.
Concerning the database: at least when using Oracle, a separate instance
does cost money, a second database user (aka namespace) is free...
Ca you use the database profix option to add in a "instance1-",
"instance2-" type prefix to each of the database tables ? Or is this
what you were sugesting ?
Chris...
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
