Moving from development box to live website

Next topic

Author	Message
Mark Irvine	Wednesday 21 January 2004 10:37:04 am Hi, I'm trying to work out if ezpublish will allow me to develop a website on a development machine, and then move the updates to a live website. I can pretty much see how to do this on a one off, first time basis. i.e copy the directory tree, then copy the database. But what about later, as the live website content gets updated, and I want to change the design by, for example,adding a new section with new templates etc? Can I change the design on the development, then move the design changes to the live site without loosing content? I obviously can't just copy the entire database this time, I'll probably lose any new content, correct? Is anybody using ezpublish in this way? What I don't want to do is make design changes on the live website. Any ideas/feedback would be appreciated. Thanks, Mark
Shurbann Martes	Thursday 22 January 2004 2:15:39 am Hi Mark, Design changes (look and feel of your site) has nothing to do with the DB, where mostly the content sits. Two things are important here: 1. the override.ini (override setting of site A: settings/siteaccess/site_A/override.ini.append) and maybe other setting files (for example image.ini.append if you have changed the image sizes in the new look etc.) 2. the design directory (override templates of site A: design/design_A/), where you have the stylesheets, images and templates When you change the look on your development server and it's working allright. The only thing you have to do is, backup the files you're going to change on the production server. And overwrite them with the new ones. In the database there's nothing stored that has something to do with the look of your site. So don't bother doing overwriting the whole DB to the production server, as you might only be losing new contents. The crucial thing here is to backup everything you're going to change. Hth, -Shurbann
Tore Skobba	Thursday 22 January 2004 2:59:11 am Hi Regarding this: >Design changes (look and feel of your site) has nothing to do >with the DB, where mostly the content sits. > Well what about about adding new classes which I often do. The definition of classes are stored in the database. However, I am gonna check out the packages system. Think that might offer an solution, but I do think it require one of the latest version, i.e. Ez 3.3-X Cheers Tore
Shurbann Martes	Thursday 22 January 2004 6:41:24 pm Yup you're right changing a class will change the DB. But till I don't think classses are part of a site feel and look. In my case everytime I add a new class on the development server, I make sure I do the same on the production server. I mean how many times are you going to change or make a new class after launching your site? (this is not THE time-consuming factor, IMHO) -Shurbann

eZ debug

Timing:	Jan 18 2025 19:34:10
Script start
Timing:	Jan 18 2025 19:34:10
Module start 'layout'
Timing:	Jan 18 2025 19:34:10
Module start 'content'
Timing:	Jan 18 2025 19:34:12
Module end 'content'
Timing:	Jan 18 2025 19:34:12
Script end

Main resources:

Total runtime	1.6505 sec
Peak memory usage	4,096.0000 KB
Database Queries	62

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	589.4688	152.6406
Module start 'layout'	0.0064	0.0041	742.1094	39.4766
Module start 'content'	0.0105	1.6386	781.5859	523.3984
Module end 'content'	1.6492	0.0013	1,304.9844	12.1250
Script end	1.6505		1,317.1094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.2165	16	0.0002
Check MTime	0.0013	0.0791	16	0.0001
Mysql Total
Database connection	0.0007	0.0448	1	0.0007
Mysqli_queries	1.5954	96.6622	62	0.0257
Looping result	0.0007	0.0443	60	0.0000
Template Total	1.5995	96.9	2	0.7997
Template load	0.0022	0.1320	2	0.0011
Template processing	1.5973	96.7737	2	0.7986
Template load and register function	0.0001	0.0085	1	0.0001
states
state_id_array	0.0020	0.1209	1	0.0020
state_identifier_array	0.0020	0.1206	2	0.0010
Override
Cache load	0.0018	0.1116	36	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0013	0.0773	3	0.0004
Fetch class attribute name	0.0028	0.1703	4	0.0007
XML
Image XML parsing	0.0004	0.0215	3	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0009	4	0.0000
General
dbfile	0.0006	0.0368	10	0.0001
String conversion	0.0000	0.0006	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
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
10	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
6	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: 22 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs