's directory structure is about the same as what I use. I would add a few specific things:
- One CVS project to rule them all.
- There's no need for MakeMaker or Module::Build if you are not creating packages for people to install on their own machines with an uncertain directory structure. A tarball is probably fine for your internal use.
- I don't put my own modules in the same place that Perl's library and site_perl stuff goes, because that stuff is owned by root. I put mine in a separate place and add it to @INC.
- Don't put ANYTHING that is not an executable or static file under your web server's docroot.
- If you use mod_perl, there's no need to put anything at all under cgi-bin. I just make PerlHandlers and map URLs to them in httpd.conf.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||