Shared var directory

Next topic

Author	Message
Lars Eirik R	Sunday 09 May 2010 3:02:14 am Hi. We are currently working on a project where we would like to have a shared var directory to store images and cache files in. Is it possible for 3 developers to share a given var directory? I am thinking about adding a symbolic link which links to shared folder on another server. I have not seen any such examples. It would be perfectly fine for each developer to have his/her own ezPublish installation, but we would like to access a share db as well as a shared var directory. Thanks
Gaetano Giunta	Sunday 09 May 2010 5:23:01 am The var dir is linked to the database. If you are having 3 developers workstations with each one having a full install (ez+db), you should share a subdirectory of var. If you are having 3 developers using the same db, the complete var dir should be shared anyway. Principal Consultant International Business Member of the Community Project Board
Bertrand Dunogier	Sunday 09 May 2010 12:16:29 pm As long as the DB is shared, and it seems to be based on your explanations, you could technically share the var directory as well... you could actually use an eZ Publish cluster for that. But having one DB / vardir with 3 different codebases might lead to unpredictable results. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Jérôme Vieilledent	Monday 10 May 2010 1:00:45 am Hi Lars As Bertrand said, the best and easiest way is to use Database Cluster mode. We use this method for big projects with a dozen of developers working in different agencies. Of course there is no problem to use database cluster mode in development and another cluster mode (eZFS2, eZDSF, ...) in production. You can easily switch from one mode to another with NovenINIUpdate extension ;-)
Gaetano Giunta	Saturday 22 May 2010 6:34:45 am For further clarification: this seems to be the case with a shared db and 3 devs having each his own workstation (or his own ezpublish install). It is a common scenario as far as I can tell: it is quite easy to have shops with 2/3 developers working on the same project, and having separate databases makes simple tasks a bit too hard (eg. can you check why node XX doe not work correctly?). To be honest, I have been developing using this model withouth a shared var directory. There are downsides, such as eg. images uploaded by dev. A not being visible by dev. B. The caches are not a huge problem in fact, as when you're developing all caches are off anyway. But the preferred method would be of course to have a var dir shared via symlink - just make sure you have no problems with filesystem permissions that would prevent one developer's post from overwriting files generated from another developer. Principal Consultant International Business Member of the Community Project Board