Hello, Today I have faced difficult problem. I have been developing application based on agavi for couple of years and regularly more people are interested to use it. Of course everybody wants to change something, add some adjustments and some features are specific for selected people. Right now file structure of my app looks like this (in terms of agavi i have created two apps):
+ backend ----- config.php ----- agavi stuff... + frontend ----- config.php ----- agavi stuff... + public_html ----- index.php (dispach frontend) ----- admin/index.php (dispatch backend) I don't know if problem is strictly connected with agavi but I want to be able to have the same base code for each interested person and be able to change only selected files (if it is possible to extend classes) like in kohana framework or magento. The perfect solution for me would be if i could create git repository for each person and install my app as two submodules[git] (frontend, backend) that would include phing build file, list of sql migrations, tests etc. I would like to be able to add two folders (for example "local-backend", "local-frontend") to this repository where i could overwrite/extend selected files. Is it possible to create such project using agavi? Do you have any ideas how to solve this problem? I would appreciate any help. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
