You just need to fire up two separate apaches, each with their own
conf. So basically you have:
/usr/local/apache_prod
/usr/local/apache_dev
These can actually share the same bin and lib directories; everything is
still installed at '/usr/local/apache' and you symlink the directories
you want
Hi there-
Apologies if this gets sent twice - I sent a message yesterday, but it
seems to have vanished into the ether.
I'd like to run the production server of my mod_perl project
(http://www.areaj.org/areaj) on the same machine as my development
server. Clearly they have the same module
Thomas K. Burkholder wrote:
run them in two different environments - I don't think running them on
two different virtual servers is going to do it, right? Doesn't apache
just start one perl runtime? Please tell me if I'm mistaken about
there is only one interpreter, so running a module
Thomas,
You can run seperate environments if your coding doesn't reference any hard
coded paths. I just setup a dev server at my new job and do exactly what
you want. All you have to do is add a use lib qw(/path/to/modules); in
your startup.pl or make sure the PERL5LIB environment var is set.
Thomas K. Burkholder wrote:
So, I guess I'm wondering if there's an easy way to have two completely
separate apache configurations running on the same machine (listening on
different ports obviously).
Hi Thomas,
just throwing a glance I found:
Ernest Lergon wrote:
just throwing a glance I found:
http://thingy.kcilink.com/modperlguide/modules/Apache_PerlVINC_Allows_Module.html
Not a good idea for production use. It will slow things down. Handy
for development with multiple projects using separate virtual hosts though.
- Perrin
