Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

My laptop has a similar setup of web server, languages, shell, etc. to both my hosting servers. My development desktop is almost exactly like my hosting servers, except it also has all my development tools and X on it (and PySol and Gweled, and even more browsers than my laptop). Then I have a testing server here in my office that I don't develop on and just test. I can completely wipe it and configure it exactly like my hosting servers or a client's third-party or in-house server.

Nothing but simple text changes go live on a client's site until it works on at least two other systems. I find tar, gzip, and scp are very helpful tool for getting the files exactly where I need them. I suggest just biting the bullet and having multiple systems.

YMMV, but I find that having clients call me and complain about lost business is a lot more hassle than an extra round of tests.

You can always, so long as you're working with allowing and denying IP ranges, deny anything outside your needed ranges for the actual, in-place directory until you're ready to launch it publicly. You could also use URL rewriting or redirection possibly also keyed to the visitor's IP.

Update: fixed a typo

In reply to Re: advice sought on perl web dev setup by mr_mischief
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 musing on the Monastery: (3)
As of 2024-06-22 17:07 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.