We have a similar issue here but it is designed more for development of
modules/code by multiple developers. This is managed through virtual hosts
and although we do not have our production server the same as development we
are able to view the production code through the development box. The
Hi all,
On Wed, 6 Feb 2002, Stathy G. Touloumis wrote:
We have a similar issue here but it is designed more for development of
modules/code by multiple developers.
If each of your developers runs her own copy of Apache, each copy
listening to a different port, you can make the namespace
Yeah, this is an ideal way to go. Althought, depending to what degree you
can trust your developers (contractors, etc.) and how much your sys admins
want to admin it may or may not be a good fit.
We have a similar issue here but it is designed more for development of
modules/code by
Sam Tregar wrote:
On Sun, 3 Feb 2002, Stas Bekman wrote:
I think the best solution is to run your staging server on a different
port and use a front-end proxy to rewrite to the right server based on
the Host: name. Alternatively put 2 NICs with 2 IPs, that will work if
you don't hardcode
On Sat, 2 Feb 2002, John Heitmann wrote:
Here is what I had to do to force correct module loading (mostly stolen
from the great mod_perl guide):
%INC = (); # Possibly unnecessary
do 'FindBin.pm';
unshift @INC, $FindBin::Bin; # There are also modules in the same dir
as the script
unshift
John Heitmann wrote:
Hello,
I have a problem, and I have a poor solution; I would like to see if I
can do even better. My problem is that I have a set of scripts and
modules that are duplicated on the same Apache server setup. One tree is
for debugging and developing, the other is the
On Sun, 3 Feb 2002, Stas Bekman wrote:
I think the best solution is to run your staging server on a different
port and use a front-end proxy to rewrite to the right server based on
the Host: name. Alternatively put 2 NICs with 2 IPs, that will work if
you don't hardcode the server name in
