Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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

In reply to advice sought on perl web dev setup by punkish

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2024-06-22 17:15 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.