best practice for eZ Publish upgrade when using SVN

Next topic

Author	Message
Greg McAvoy-Jensen	Friday 12 September 2008 8:54:23 pm If one is using Subversion to deploy to the testing/staging server and production server (as well as development machines), what is the best step-by-step process for upgrading eZ Publish? Assume we're using the directory structure of the "myproject" example in Jérôme Renard's article (http://ez.no/developer/articles/using_subversion_with_ez_publish/common_problems_and_solutions) (but without having the database under version control). My initial thought would be: 1. Backup. 2. Create a fresh installation of the new eZ Publish version in a directory called ezpublish-x.y.z. 3. Copy site-specific to new installation. 4. svn import ezpublish-x.y.z svn://example.com/path-to-repository/trunk/ezpublish-x.y.z. 5. Each developer can then svn checkout the new version, point it at their database, run the database upgrade script, and point Apache to new the new directory. 6. svn copy svn://example.com/path-to-repository/trunk/ezpublish-x.y.z svn://example.com/path-to-repository/branches/testing/ezpublish-x.y.z. 7. On the testing server, svn checkout the new version, point it at the testing database, lock down the database, copy over the old var directory (and needed ini files), run the database upgrade script, point Apache to the new directory, and unlock the database. 8. On the production server, svn checkout the new version, point it at the testing database, lock down the database, copy over the old var directory (and needed ini files), run the database upgrade script, point Apache to the new directory, and unlock the database. Is this the most efficient way to handle it? What improvements could be made? On a live server where one does not have root access and relies on the host system administrators to point Apache to the new directory, is it best to have a sym link (link www to ezpublish-x.y.z) so we can re-point it ourselves (assuming following sym links is allowed)? Thank you for your input. Granite Horizon, Certified Developer of eZ Publish Web Solutions Provider of the SaaS Solution Granite Horizon In The Cloud \| http://granitehorizon.com/cloud http://granitehorizon.com \| +1 916 647 6350 \| California USA \| @granitegreg Blog: http://granitehorizon.com/blog

Author

Message

Friday 12 September 2008 8:54:23 pm

If one is using Subversion to deploy to the testing/staging server and production server (as well as development machines), what is the best step-by-step process for upgrading eZ Publish? Assume we're using the directory structure of the "myproject" example in Jérôme Renard's article (http://ez.no/developer/articles/using_subversion_with_ez_publish/common_problems_and_solutions) (but without having the database under version control).

My initial thought would be:

1. Backup.
2. Create a fresh installation of the new eZ Publish version in a directory called ezpublish-x.y.z.
3. Copy site-specific to new installation.
4. svn import ezpublish-x.y.z svn://example.com/path-to-repository/trunk/ezpublish-x.y.z.
5. Each developer can then svn checkout the new version, point it at their database, run the database upgrade script, and point Apache to new the new directory.
6. svn copy svn://example.com/path-to-repository/trunk/ezpublish-x.y.z svn://example.com/path-to-repository/branches/testing/ezpublish-x.y.z.
7. On the testing server, svn checkout the new version, point it at the testing database, lock down the database, copy over the old var directory (and needed ini files), run the database upgrade script, point Apache to the new directory, and unlock the database.
8. On the production server, svn checkout the new version, point it at the testing database, lock down the database, copy over the old var directory (and needed ini files), run the database upgrade script, point Apache to the new directory, and unlock the database.

Is this the most efficient way to handle it? What improvements could be made? On a live server where one does not have root access and relies on the host system administrators to point Apache to the new directory, is it best to have a sym link (link www to ezpublish-x.y.z) so we can re-point it ourselves (assuming following sym links is allowed)?

Thank you for your input.

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

eZ debug

Timing:	Jan 19 2025 04:29:43
Script start
Timing:	Jan 19 2025 04:29:43
Module start 'layout'
Timing:	Jan 19 2025 04:29:43
Module start 'content'
Timing:	Jan 19 2025 04:29:44
Module end 'content'
Timing:	Jan 19 2025 04:29:44
Script end

Main resources:

Total runtime	0.4936 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	590.3984	152.6406
Module start 'layout'	0.0044	0.0021	743.0391	39.4922
Module start 'content'	0.0065	0.4859	782.5313	475.9297
Module end 'content'	0.4923	0.0012	1,258.4609	8.1250
Script end	0.4936		1,266.5859

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	0.5181	16	0.0002
Check MTime	0.0011	0.2328	16	0.0001
Mysql Total
Database connection	0.0008	0.1588	1	0.0008
Mysqli_queries	0.4595	93.0911	46	0.0100
Looping result	0.0005	0.0987	44	0.0000
Template Total	0.4698	95.2	2	0.2349
Template load	0.0016	0.3264	2	0.0008
Template processing	0.4682	94.8568	2	0.2341
Template load and register function	0.0001	0.0205	1	0.0001
states
state_id_array	0.0010	0.2079	1	0.0010
state_identifier_array	0.0005	0.1043	2	0.0003
Override
Cache load	0.0013	0.2719	16	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1366	1	0.0007
Fetch class attribute name	0.0009	0.1902	2	0.0005
XML
Image XML parsing	0.0006	0.1296	1	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0007	2	0.0000
General
dbfile	0.0008	0.1652	18	0.0000
String conversion	0.0000	0.0011	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 7 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs