Migration from dev to prod

«

Previous topic

|

|

Next topic

»

Author	Message
John Moritz	Wednesday 15 October 2008 7:32:55 am At the moment i am developing a Site using ezPublish 4.0.1, local on vmware. I thinking about what do to, to make a clean migration from my development Server to production Server. I installed 4.0.1 on both servers. Is it save to make a dumb of the dev database and copy it to the production server? What else must i do to have a working Production server after migrating?
Nabil Alimi	Wednesday 15 October 2008 9:19:36 am Hi John, You first need to copy developpement files from dev to prod. In normal cases that should be : - design/example - settings/siteaccess - settings/override - extension provided you haven't done any kernel changes, that should do. Next step is to do just as you said : transfer your dev database onto your prod server. Make sure to configure the database settings and such things in order to suit the new server requirements and login policies. My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com eZ Publish Freelance developper. Feel free to contact me +33 674 367 057 nabil at assiki d0t fr
Greg McAvoy-Jensen	Wednesday 15 October 2008 12:01:20 pm You'll also want to take the var directory, which must be completely in sync with the database (copied at the same instant, or copied while the database is locked down). And, of course, you'll need to change your site.ini files to match the production server environment. 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
John Moritz	Wednesday 15 October 2008 2:12:08 pm Thanks to you guys. I think thats everything i needed to know.

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 19 2025 07:18:14
Script start
Timing:	Jan 19 2025 07:18:14
Module start 'layout'
Timing:	Jan 19 2025 07:18:14
Module start 'content'
Timing:	Jan 19 2025 07:18:14
Module end 'content'
Timing:	Jan 19 2025 07:18:14
Script end

Main resources:

Total runtime	0.0157 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0062	590.2734	152.6250
Module start 'layout'	0.0062	0.0026	742.8984	39.4453
Module start 'content'	0.0088	0.0048	782.3438	93.3203
Module end 'content'	0.0136	0.0021	875.6641	34.3047
Script end	0.0157		909.9688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.8001	14	0.0002
Check MTime	0.0010	6.6744	14	0.0001
Mysql Total
Database connection	0.0010	6.3516	1	0.0010
Mysqli_queries	0.0022	13.9553	3	0.0007
Looping result	0.0000	0.0834	1	0.0000
Template Total	0.0017	10.9	1	0.0017
Template load	0.0010	6.4850	1	0.0010
Template processing	0.0007	4.4264	1	0.0007
Override
Cache load	0.0007	4.4506	1	0.0007
General
dbfile	0.0003	1.7190	8	0.0000
String conversion	0.0000	0.0515	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs