Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
My solution would probably depend in some measure on the sensitivity of the material to go into /mydynamic and the relationship between the pages in mystatic and those in /mydynamic (e.g., is there a subordination relationship between multiple static pages and one or more dynamic pages).

If the sensitivity is low and the relationships dependant only links from only a very few static pages, it may even be practical to rely on (gaghhh! I know no-one here ever expected this from me.) the truly lousy option of "security by obscurity."

The "few" consideration comes in here: Create a mystatic^test.htm based on each parent mystatic.htm, adding a link to the relevant child-generating CGI::App script, and deploy it and the CGI::App script (obviously, after careful testing on your laptop) to the public-facing server.

Potential problems: all those you've listed, all those associated with any attempt at security by obscurity; and the need for cleanup later.

But if the risks of penetration (associated with having artistes of evil or the random set of folks who make just the right typo access your new material) are truly low, this might present a lower cost solution than putting a pure dev-server on line.

In reply to Re: advice sought on perl web dev setup by ww
in thread 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 cooling their heels in the Monastery: (3)
As of 2024-05-24 02:37 GMT
Find Nodes?
    Voting Booth?

    No recent polls found