Having managed this sort of configuration with MediaWiki, I've had thoughts about using it for hosting Koha instances. It has a number of advantages, including being more amenable to mod_perl. The biggest drawback to this configuration is when applications care about the port number on which the HTTP daemon received a request (as MediaWiki does) since it's invariably not the port that you want further requests to go to. Have you experienced issues like that with Koha?
Clay On Tue, Nov 25, 2008 at 3:14 AM, Rick Welykochy <[EMAIL PROTECTED]> wrote: > Paul POULAIN wrote: > >> Michael Hafen a écrit : >>> Hmm, I hope that isn't the case. I have multiple instances of Koha >>> running on a server with mod_perl installed. I haven't heard any >>> complaints so far. >> >> wow... are you sure you're with mod_perl ? we did some test, on a small >> library, and the result was awful (with duplicated biblios, and other >> blockquing problems) > > Yup, that backs up my general experience with mod_perl. > > If you have multiple definitions of environment variables and > attempt to load different instances of the same perl modules (for > example) all chaos breaks out. > > The solution: one instance of apache for each instance of Koha > that you require. > > We are running about ten Kohas on one machine. Each uses its own > instance of Apache. Nice and clean and most importantly: safe. > > > cheer > rickw > > > -- > _________________________________ > Rick Welykochy || Praxis Services > > Tis the dream of each programmer before his life is done, > To write three lines of APL and make the damn thing run. > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
