Re: Directory Structures

This is what I usually use:

ProjectName/
ProjectName/code/
ProjectName/code/bin/ - main script.pl and shell scripts for calling i
+t with params
ProjectName/code/bin/log/ - log files
ProjectName/code/bin/resource/ - config files etc
ProjectName/code/lib/
ProjectName/code/lib/My/Project/Modules/
ProjectName/code/t/
ProjectName/notes/
ProjectName/release/ - make scripts, binaries, and installers
[download]

Comment on Re: Directory Structures Download Code

Replies are listed 'Best First'.
Re: Re: Directory Structures by artist (Parson) on Jan 30, 2003 at 01:00 UTC
Hi Jplindstrom ProjectName/code/bin/log/ - log files ProjectName/code/bin/resource/ I had the idea that bin contains files to execute. Log files and resources should not be in a seperate directory?. What type of file structure within 'notes' and release? Besides that where do you keep other programs, such as testing modules, perlmonks answer scripts etc, your own common modules and snippets.. Thanks, artist	[reply]
Re: Re: Re: Directory Structures by jplindstrom (Monsignor) on Jan 30, 2003 at 19:06 UTC
I had the idea that bin contains files to execute. Log files and resources should not be in a seperate directory?. I see that directory as "the application directory", i.e. it contains the actual program (the .pl file) and the things it needs. It works fine with the way I do things. If you think your program logs should be a level up, I don't see why you shouldn't do that. What type of file structure within 'notes' and release? The "notes" dir is free-form. It's too varied between projects to specify in any more detail. The release dir just contains scripts for making a release, and versioned zipped files or installers for each release. The "t" directory contains module tests obviously. /J	[reply]