I second that - it is a security risk.

I do like both Coreolyn & Fastolfe's ideas. I am trying to organize my projects better these days but so far I keep changing my mind each time I start a new one. At least it's better than when I used to dump EVERYTHING in one folder.

My current directory plan is a bit like this: 
/work/project-a/database  -  store databases in here
/work/project-a/libs      -  modules, libraries
/work/project-a/temp
/work/project-a/backups   -  archives of previous working versions
/work/project-a/webroot   -  Web folder starts here
/work/project-a/utils     -  command line utils I may need
/work/snippets            -  useful code snippets to save and reuse.

[download]
I like Fastolfe's use of a docs folder. I really, really, really should do that. Problem is, I work in a company where I'm the only guy who can 'use Perl;' - everyone else uses VB\VBScript. Maybe that's a reason TO document more?

Update: To answer ichimunki's second question, (if I understand it correctly), so long as you don't rely on anything above your project root and use relative links, then you should be able to zip up the project folder when you are ready to move from development to production, or whatever.

In reply to ($code or die) Re: Development Directory Structure and Technique by $code or die
in thread Development Directory Structure and Technique by ichimunki

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.