svn (cvs) strategies ?

svn (cvs) strategies ?

Friday 14 November 2003 3:02:53 am - 2 replies

Author Message

Bård Farstad

Friday 14 November 2003 3:41:42 am

Thomas,

what I normally do when I set up a site is to have the directories settings/siteaccess/mysite_user, settings/siteaccess/mysite_admin and design/mysite in a svn repository. Then I can version control my own changes for the specific project. You need a separate svn server/repository to do this.

You should not need to change kernel sources for your projects, if you need to do this you should use the plugin system for the part you need. E.g. write a new datatype, module or template operator.

I would normally not use the svn version of eZ publish ( unless it's the stable branch ) for a project.

Then when I update the live server ( e.g. ez.no ) I just do an svn up on this server to get all my local changes upgraded. If things go very wrong you can always back up to the previous version with svn, which is very nice.

--bård

Documentation: http://ez.no/doc

Paul Forsyth

Friday 14 November 2003 4:47:50 am

Have a read here too:

http://ez.no/developer/ez_publish_3/forum/developer/cvs_and_ez_32_developing

paul

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

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.