On 5/16/07, Tony Harrison <[EMAIL PROTECTED]> wrote:
It is mostly a separate application, but I want them to share some files.
IMO, it's not worth the hassle. If you use the same models/classes, first create two seperate virtualhosts (in the webserver), then create an SVN repository for them and "svn up" to deploy the changes. I also don't like linking the Zend Framework via include_path, so different apps share the same class files. IMO the hassle of updating all your apps vs. one at a time (e.g. a new version of the ZF is released) is generally slowing you down. It also doesn't guarantee quality since the update might break five applications instead of one. And creats a flood in my issue tracker. ;-) Last but not least, whatever happens when you need to farm out your apps? I like to keep things together. So basically, I like to deploy a tarball and have all dependencies included. Hope that helps, Till
