Optimal Folder structure of a Zend Framework Project for future growth
Hi All,
I am building a software that is going to be used by many users.
Each user will have his/her own area to upload files.
Some clients may require a customized version of the software.
My code start with "My" prefix and follows Zend Framework's class conventions.
My and Zend Framework's code may need to be shared among the installations.
It'll run on a linux/unix server.
Could you give me some suggestions how to organize the folder structure to be easy for future updates.
Option #1
Public area
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
library/Zend
library/My
Option #2
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
/usr/local/myproduct/libra
/usr/local/myproduct/libra
Option #3 (best option ?)
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
I am building a software that is going to be used by many users.
Each user will have his/her own area to upload files.
Some clients may require a customized version of the software.
My code start with "My" prefix and follows Zend Framework's class conventions.
My and Zend Framework's code may need to be shared among the installations.
It'll run on a linux/unix server.
Could you give me some suggestions how to organize the folder structure to be easy for future updates.
Option #1
Public area
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
library/Zend
library/My
Option #2
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
/usr/local/myproduct/libra
/usr/local/myproduct/libra
Option #3 (best option ?)
www/themes
www/modules/module1/image
www/modules/module1/css
www/modules/module1/js
Non-public area
app/application/controller
app/modules
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
/usr/local/myproduct/1.0.0
Take a look at the folder structure that is created using the new Zend_Tool project generator (http://framework.zend.com/manual/en/zend.tool.project.html). This is the defacto "conventional" project structure which will match up with with the defaults set within the framework as well as with most tutorials and documentation.
ASKER
Thanks for the reply.
What I am looking is how to organize the folder structure to be able to handle future growth and also updates in different modules.
Let's say my software will be used by thousands of users.
Thanks again.
What I am looking is how to organize the folder structure to be able to handle future growth and also updates in different modules.
Let's say my software will be used by thousands of users.
Thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks.
That's a good idea to put shared code in a separate folder.
That's a good idea to put shared code in a separate folder.