I'm for the first option. Just simply use symlinks or include path (anyway, longer include path could add some stat calls). Supposing you have a main "library" (like with pear, in /usr/share or similars) ZF will be loaded from there by every project. Thus, APC Opcode cache should resolve always to the same location. This is the best in terms of performance, but requires you to check for BCs as youy said. Anyway, ZF 1.X should probably become more like a stable security-fix-mantained version after ZF2. Therefore, if those updates are not vital to your project, just take some time and try to read all changelogs. My 2 cents :)
Marco Pivetta @Ocramius <http://twitter.com/Ocramius> http://marco-pivetta.com On 10 April 2011 15:28, Jurian Sluiman <[email protected]> wrote: > Hi all, > > With several ZF projects on one server and each a default config (Zend and > ZendX libraries in the library/ folder of a project) we have many ZF > libraries > on our system. > > Not all versions are the same but we'd like to reduce the number (mainly > because of APC performance). We run Zend Server CE and have zend-server- > framework installed. What is the best option? > > 1) All projects use the /usr/local/zend/share/ZendFramework/library/Zend > lib > 2) We install our own /usr/local/zend-framework/1.11.5/Zend libs > 3) Status quo (libraries per project) > > For 1) we need to make sure all projects still work after an update. With > BC > breaks, it can cost suddenly a serious amount of time to fix it. Advantage: > simple update, all in one place. > For 2) we don't need to worry about the different versions, because we > install > the libraries under different version numbers. > For 3) I don't think it's the best option, but maintainability is the best. > > The next thing is namely not to worry about production, but rather > development > environments: how do we manage keeping the libraries in a custom place for > all > different developers? > > I'd like to hear your thoughts, > Jurian > -- > Jurian Sluiman > Soflomo - http://soflomo.com > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
