svn (cvs) strategies ?

Author Message

Thomas Thiel

Friday 14 November 2003 3:02:53 am

hi,
hoping not being too far off topic I would like to ask you for your specific strategies setting up and maintaining your svn/cvs-repository of ezp3 together with your own modifications.
I regularly update my svn-checkout from ezp-svnserver. Quite often I also adapt/extend kernel-sources to my needs. These adaptations I also want to bring into the svn - together with the downloaded svn-modifications from eZSystems.

And then there are a lot of client-specific .tpl and .ini-adaptations that should be saved together with the specific design-ressources.

How do you accomplish this? Read svn-docu several times but maybe I'm too stupid to set up a svn-design and strategy to fit the described needs.

Thanks in advance,

Thomas

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

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

eZ debug

Timing: Jan 31 2025 01:29:23
Script start
Timing: Jan 31 2025 01:29:23
Module start 'layout'
Timing: Jan 31 2025 01:29:23
Module start 'content'
Timing: Jan 31 2025 01:29:23
Module end 'content'
Timing: Jan 31 2025 01:29:23
Script end

Main resources:

Total runtime0.0280 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0051 588.0156151.1953
Module start 'layout' 0.00510.0036 739.2109220.6719
Module start 'content' 0.00870.0167 959.8828997.7734
Module end 'content' 0.02540.0025 1,957.656333.9922
Script end 0.0279  1,991.6484 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.003111.1577140.0002
Check MTime0.00124.2045140.0001
Mysql Total
Database connection0.00082.743610.0008
Mysqli_queries0.00289.879130.0009
Looping result0.00000.053710.0000
Template Total0.00196.810.0019
Template load0.00165.841610.0016
Template processing0.00030.982110.0003
Override
Cache load0.00134.551110.0013
General
dbfile0.00196.684080.0002
String conversion0.00000.028140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs