http://www.perlmonks.org?node_id=838237

punkish has asked for the wisdom of the Perl Monks concerning the following question:

The title is ambiguous. Here goes...

I am developing a complicated web site with both static and dynamic components like so --

http://mystatic/ http://mystatic/mydynamic/

All URIs under /mystatic are static html, except under mystatic/mydynamic/ which are powered by Perl (CGI::App).

I am developing this on my laptop, and also have a public facing web server with the http://mystatic stuff (no mydynamic stuff on the web server yet) already installed and running.

I would like to also share my developments with my team (my testers) via a staging server which would be accessible at http://mystaging/mystatic/mydynamic/

Obviously, this entails me having to set up and maintain 3 different Perl instances, which, along with different URLs (the web server has DNS names, while the staging server has directory aliases), makes for a royal pain in the ass from a maintenance perspective.

What suggestions do you have?

One thought I've had is to do away with the staging server. Instead, stage my work in progress right on the public webserver, but under a URI that is accessible only from an internal range of IP addresses. So, for example, put a "coming soon" page under http://mystatic/mydynamic/comingsoon.html, but put the work in progress under http://mystatic/mydynamic_dev/, and restrict access to mydynamic_dev using Apache's rules for Allow,deny. That way I have to deal with only two Perl installations. Of course, if I bugger up, I mean, if I experiment with a Perl module, and mess something up, there is the likelihood that everything will go kerplunk, but with care, it could work.

What would monks do?

--

when small people start casting long shadows, it is time to go to bed