I'm not sure if you wish to hear what others use for Perl projects or programming projects in general (ie: any language). Since almost all of what I do is done in Perl, I'll assume the former. Also, I don't do very many command-line scripts, as I usually deal with CGI applications. So my CGI approach is what I will post.

This node has been considered with a reason of 'Why is this frontpaged? This is not a perl question'. No, it is not directly related to perl, but perl is definitely a subset of the question asked, so it is a perfectly valid question to be posted, as well as frontpaged. I was rather pleased to see such a question posted, as it offers a break from the usual programming questions. Perl is used for development, so some development questions are going to rise to the sufrace, and it seems prfectly alright by me.

Now on to my general CGI application directory structure. As already noted, this actually changes on a per-project basis. Time to use <pre></pre> tags for the first time (ack!). (Base directory is '/var/www/Port80/ProjectName'): 

.htaccess       - Sets project-wide directives

bin/            - Project's command-line tools
    .htaccess   - Deny web access
    readme.txt  - Contains description of all tools

cgi-bin/           - Contains web-accessible perl scripts
        .htaccess  - Enable CGI, desired directives

images/             - Contains all images used
       readme.txt   - Describes subdirectories
       corporate    - Corporate logos, etc.
       display      - Backgrounds, border images, etc.
       incoming     - If I have user-uploaded images

logs/               - Any log files used
     readme.txt     - Explanation of log contents/format

modules/
        .htaccess   - Deny web access
        readme.txt  - Descriptions of contained modules
       


      C:\>shutdown -s
      >> Could not shut down computer:
      >> Microsoft is logged in remotely.

In reply to Re: Directory Structures by Coruscate
in thread Directory Structures by artist

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.