Re: Development Directory Structure and Technique

I'm looking forward to seeing answers to this one myself, as I've experimented with several styles/structures and I'm not 100% content with any of them. In the spirit of sharing, here's the structure I've evolved:

#root (primary executable scripts)
apache_root/projectname

# project maintenance scripts
apache_root/projectname/scripts<sup>1</sup>

# modules
apache_root/projectname/lib

# Archives (place where maintenance scripts 
# pput backup .tgz's)
apache_root/projectname/dist
[download]

Looking at projects via CVS is a good way to see how other's do it, though I do not see any standard pattern accross various projects emerging.

coreolyn

¹ I reccommend NEVER to use a 'bin' directory in your projects lest a hasty script or typo waste your systems /bin (Not that I've learned that the hard way ;)

Comment on Re: Development Directory Structure and Technique Download Code

1 I reccommend NEVER to use a 'bin' directory in your projects lest a hasty script or typo waste your systems /bin (Not that I've learned that the hard way ;)

¹ I reccommend NEVER to use a 'bin' directory in your projects lest a hasty script or typo waste your systems /bin (Not that I've learned that the hard way ;)