Hi, after two days of thinking and trying we're now out of ideas. :-/
This is the problem: As many others we've customized and extended Zend Framework to our needs. The idea behind this "core" is to use it as base for all new applications by adding them as module. In favor of an easier update management and transparency we'd like to keep the core sources and the project sources separate. In our core we have the following structure: - application => The default module with all core-Controllers, -models, views ... - config => The core-relevant config-files - html => Our document root with index.php and the styles, scripts, etc. used in core We thought of the following structure for our applications: - application => The module(s) of our applications - config => Application-specific config files - html => The application specific "public" files (styles, scripts, images and so on) Both the core and the applications have their own SVN-repositories. Changes to the core should smoothly be introduced to the applications. No we've discussed a few possibilites to implement this structure and experimented with some approaches but did not get to a satisfying solution and now we hope that anybody around here has an idea. Things we tried: 1. Treat the core as vendor branch in the project repository and merge changes. Pro: Relatively easy update process for changes in the core. Con: Huge redundancy of code; Dependency on Subversion 2. Symlink the application folders to the corresponding core folders Pro: Separation of code, easy integration of changes Con: Dependancy on *nix - Some developers work on a local XAMPP 3. Keep the core and the application in different folders. Make the application-html-folder document root and fetch the Core-files through a not further specified mechanic. Con: No idea how to implement the mentioned mechanic. Any suggestions to solve our dilemma? Thanks in advance, René -- View this message in context: http://www.nabble.com/Reuse-customized-ZF-tp21482046p21482046.html Sent from the Zend Framework mailing list archive at Nabble.com.
