Re: different versions of same Perl module in different Apache vhosts

You can use Apache::PerlVINC, although it may affect your performance. The recommended approach is to start two separate servers. You can use the same apache and just start it on two different ports with separate config files. Change @INC inside each one to point to the correct version of your modules.

Comment on Re: different versions of same Perl module in different Apache vhosts

Replies are listed 'Best First'.
Re^2: different versions of same Perl module in different Apache vhosts by agaffney (Beadle) on Jun 05, 2004 at 23:43 UTC
Would I need to use it in both vhost definitions? Could I just leave the primary alone and put the development module in some other dir and use Apache::PerlVINC with the development vhost definition? I can live with degraded performance on just the development site.	[reply]
Re^3: different versions of same Perl module in different Apache vhosts by perrin (Chancellor) on Jun 07, 2004 at 02:33 UTC
I'm not sure about this, since I've never used Apache::PerlVINC. It seems like it should work, but would probably still affect performance in both. I think Apache::PerlVINC causes the modules to be re-compiled every time, which is a performance hit, and will ruin the copy-on-write shared memory that mod_perl would otherwise benefit from.	[reply]