Hi, just use magic...: 1. move your test modules to /path/TEST/YourPrefix/name.pm 2. add /path to @INC (NOT /path/TEST !) 3. add PerlSetVar test TRUE for your test virtual host and change the PerlHandlers to read TEST::YourPrefix::name 4. write a Filter that does something like if ($r->dir_config('test') { s/YourPrefix::/TEST::YourPrefix::/g; } 5. USE your new Filter in all Modules BEFORE the "package"-line Now Perl will see your test modules as TEST::YourPrefix::name and the normal modules als YourPrefix::name. No changes are necessary when migrating tested modules to production. Abracadabra and done. cu/2 Michael Jacob PS: Or just run 2 Apache instances with different @INCs. That's easier... Datum: 17.11.2000 17:15 An: [EMAIL PROTECTED] Betreff: trying to isolate VirtualHosts running identical .pm's Nachrichtentext: I'm trying to configure a single box to host completely separate instances of development and test versions of the same code base (currently 49 modules). Right now I have 2 virtual hosts configured on the same IP and servername, but use different ports, i.e., 80 and 82. I attempted to use PerlSetEnv PERL5LIB /usr/local/lib/perl5/site_perl/5.005/sun4-solaris:/path/to/mydevel or, PerlSetEnv PERL5LIB /usr/local/lib/perl5/site_perl/5.005/sun4-solaris:/path/to/test in each respective's <VirtualHost> section, but this did not work. /perl-status?inc always shows: @INC = /usr/local/lib/perl5/5.00503/sun4-solaris /usr/local/lib/perl5/5.00503 /usr/local/lib/perl5/site_perl/5.005/sun4-solaris /usr/local/lib/perl5/site_perl/5.005 . /usr/local/apache/ /usr/local/apache/lib/perl I then tried PerlVINC (version 0.03) by adding to my devel virtualhost section: PerlModule Apache::PerlVINC PerlINC /path/to/mydevel/ PerlFixupHandler Apache::PerlVINC PerlCleanupHandler Apache::PerlVINC # PerlVersion Apache::TicketMaster but then get an error if I uncomment out the above line, saying that it can't locate TicketMaster in @INC ... Assuming I could get the above to work for a single module (by reloading it with PerlVersion), is there any way to globally force the server to execute the proper module, depending on which virtualhost it's serving, without having to explicitly do a reload of each individual module (potentially > 50)? Thanks in advance, Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]