If you have relatively simple CGI scripts on Windows, a tool called "OptiPerl" from Xarka has most of an IDE, plus a mini-webserver that allows you to view the outputs as web pages. I haven't been down the road of reevaluating *nix Perl IDEs lately (although I imagine there are some good plugins for NetBeans and Eclipse by now; I've been sticking to the "Unix IS the IDE" mentality), but I know from working with NetBeans and Eclipse for Java that they do offer something similar.
Once you start getting complicated enough, it makes sense to just to write a script to set up your development environment and require that Apache (or whatever) be a part of that.
Something we often do for testing is set up a single-instance webserver on a nonprivileged port; this is generally enough for day to day, and as long as it's actually CGI and not mod_perl or similar, you can use a very low key webserver. Of course, there's nothing like testing in the exact environment in which you anticipate deployment.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.