One solution could be to put your modules in some nonstandard location and include them in @INC in the mod_perl_start.pl. Then just use two different locations for the modules, and each server adds one of these locations into @INC - so production modules go to production server's @INC and dev goes to dev server's @INC...
Issac Internet is a wonderful mechanism for making a fool of yourself in front of a very large audience. --Anonymous Moving the mouse won't get you into trouble... Clicking it might. --Anonymous PGP Key 0xE0FA561B - Fingerprint: 7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B ----- Original Message ----- From: "raptor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 30, 2001 17:08 Subject: site copies under the one httpd > hi, > > I have a site, it has two copies one that is on the Dev server (dev-copy) > and the other Production one. > So what I want ? > I want to have the Production site on my dev machine ... ( i'm arraging that > the DB and all dependant stuff get copied after some time passes). But AS U > KNOW I can't have two different modules with the same name under one > mod_perl even if they are on different virtual-hosts, 'cause they get > precompiled under the same name... > Is the only solution to use differnt mod_perl processes to handle this > situation ?!! > ===== > iVAN > [EMAIL PROTECTED] > ===== >
