Development Directory Structure

Question

I am wondering what directory structure is commonly used in development projects. I mean the idea of ​​facilitating assembly, deployment deployment, etc.

I recently used the Maven framework for a java project, but I'm not sure if this is the best framework for a non-maven managed project.

So, I have two questions: when you guys start new projects, what structure do you use? And: What if you need to integrate two different languages, for example, for example, Java classes in a PHP application; PHP files are source files, web files, do you use / src, / classes, webapps / php? What is your choice in such scenarios.

As a side note: I'm also wondering what options you have for directory names. I like 3 letter names (src, lib, bin, web, img, css, xml, cfg), but what are your opinions on descriptive names like libraris, sources or htdocs / public_html?

Answer 1

After a couple of years, working with different structures, I recently found a structure that interests me the most:

/project_name (everything goes here) /web (htdocs) /img /css /app (usually some framework or sensitive code) /lib (externa libs) /vendor_1 /vendor_2 /tmp /cache /sql (sql scripts usually with maybe diagrams) /scripts /doc (usually an empty directory) 

Answer 2

Although we do not use Maven, we use the Maven directory structure.

We found that it accurately reflects the concepts we need (for example, dividing the deployment code into test code, code from data, installers from code). We also believe that if one day we switch to Maven, most of our process will remain the same.

Answer 3

I just found an interesting document on directory structures on the Zend website:
http://framework.zend.com/wiki/display/ZFDEV/Choosing+Your+Application%27s+Directory+Layout

Answer 4

2011 update: http://java.sun.com/blueprints/code/projectconventions.html