eZ Community » Forums » Developer » Subversion and var/storage
expandshrink

Subversion and var/storage

Subversion and var/storage

Saturday 07 June 2008 8:33:22 am - 5 replies

I've read posts about handling var/cache and var/log with svn:ignore. That makes sense. But should var/storage be handled the same way? What makes the most sense?

Saturday 07 June 2008 11: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

Modified on Saturday 07 June 2008 11:41:33 am by Gaetano Giunta

Saturday 07 June 2008 3:39:53 pm

Thanks, Gaetano.

That's what I thought, but wanted to be sure I wasn't missing something since the article (http://ez.no/developer/articles/using_subversion_with_ez_publish) listed var/cache and var/log but not var/storage or simply "var".

Monday 23 June 2008 8:30:45 pm

One follow-up question: does this mean that if we're using the ignore property on the var directory, we should never use svn commit from the root ezpublish directory?

I'm new to SVN, and assumed after doing whatever changes I wanted (template override settings, extension design, etc.) I would then just do a svn commit from the root ezpublish directory--but this updates the var directory even with propset ignore. Am I missing something?

And is the same true on the testing and production servers--we should only use svn update on the specific directories we've made changes to? It seems to make us more prone to errors.

Thanks for any thoughts.

Thursday 27 January 2011 3:02:36 am

Hi Greg,

Another point you can focus on : some extension are generating data inside the extension and not inside the var directory.

Typically ezfind has its own index under /extensions/ezfind/java/solr/data.

Max

Saturday 29 January 2011 11:33:17 am

@maxime a good point. And I think we should in fact fix those extensions,as the 'ez' way is to only have variable data in /var.

Apart form ezfind, any other known offender?

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from