Saturday 07 June 2008 2:41:09 am
It makes sense to svn:ignore var/storage too for the two simple reasons: - it will grow very big very fast, and putting it in svn will make your svn crawl to a grinding halt - especially if you keep your workspace on windows (not even taking into account a possible antivirus), but on unix too (just svn delete of the var/storage dir when linked to repo over https over internet took me an hour or so) - as soon as you have made a first copy of your dev server install to a test, integration or production setup, the different installs will diverge as for content present. Devs will create test content in the dev eZ to check out new templates, editors will usually start to fill in real content in the integration or prod installs, etc. Some identical content will be created by hand in both eZP installs, resulting in different files in var/storage In short: have svn ignore it. When you need to resync your data from eg. prod to dev, copy over at the same time both the db and the storage, and you're done
Principal Consultant International Business
Member of the Community Project Board
|