Another SiteURL question

Next topic

Author	Message
Hardy Pottinger	Wednesday 09 June 2004 11:59:13 am I'm setting up subversion (SVN) to track our ezpublish-based projects, and am slowly working towards the best way to do this (based on a few postings to the forums, and my own experiments). In order to support multiple version of the same site (each developer will have their own working copy), I think I can get away with just adding each site's URL to HostMatchMapItems in settings/override/site.ini.append.php: HostMatchMapItems[]=SITE.domain;site HostMatchMapItems[]=admin.SITE.domain;site_admin HostMatchMapItems[]=SITE.testdomain;site HostMatchMapItems[]=admin.SITE.testdomain;site_admin HostMatchMapItems[]=SITE.developer.testdomain;site HostMatchMapItems[]=admin.SITE.developer.testdomain;site_admin And then I seem to be able to just delete SiteURL from settings/siteaccess/SITE/site.ini.apppend and settings/siteaccess/SITE_admin/site.ini.apppend <b>Here's my question. While this seems to be working at the moment, is there any reason I shouldn't do things this way?</b> I plan to use the same database on the development server for all the developers, as well as the test/staging site.
Paul Forsyth	Wednesday 09 June 2004 12:16:39 pm This is very similar to the way we work. We also have SVN as our back end repository and set up developer matches in the site.ini to stop the file from needing to change too often. Do your developers have a local db too? We find this useful <b>during</b> development, to test things, to break things etc. Though the l/p for the db user should be the same. When the transition to the live box occurs this needs to change. We also find this tool useful for viewing the svn repository: http://websvn.tigris.org/ paul -- http://www.visionwt.com
Hardy Pottinger	Wednesday 09 June 2004 12:55:52 pm > Do your developers have a local db too? They can, but for now, we're going to stick with everyone using the same development database, until we need to have seperate databases. That will let us all kind of work from the same content, and may provide an impetus to communicate ("what's this object of yours? it sounds interesting..." etc.) If you have seperate databases, do you make any effort at periodically syncing them together?
Paul Forsyth	Wednesday 09 June 2004 1:00:31 pm Absolutely. We do sync regularly and maintain the notion of who has the live db. Having local the db is just a test bed while things become sorted. The live db can be accessed and added to by anyone, then exported out again. Not long into a project this stabilises and only content is added to the live db. I should stress we haven't scaled this process but it works for the people we have. paul -- http://www.visionwt.com
Hardy Pottinger	Wednesday 09 June 2004 1:47:55 pm > Absolutely. We do sync regularly Say, if you have this scripted, and it's not too much to ask, can you post your script? Actually, I think it would be really great if we could get a pile of everyone's automation scripts for working with version management systems.

eZ debug

Timing:	Jan 19 2025 04:15:38
Script start
Timing:	Jan 19 2025 04:15:38
Module start 'layout'
Timing:	Jan 19 2025 04:15:38
Module start 'content'
Timing:	Jan 19 2025 04:15:39
Module end 'content'
Timing:	Jan 19 2025 04:15:39
Script end

Main resources:

Total runtime	0.8073 sec
Peak memory usage	4,096.0000 KB
Database Queries	63

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	589.1563	152.6250
Module start 'layout'	0.0063	0.0029	741.7813	39.4453
Module start 'content'	0.0091	0.7967	781.2266	530.7656
Module end 'content'	0.8058	0.0015	1,311.9922	16.1641
Script end	0.8073		1,328.1563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.4157	16	0.0002
Check MTime	0.0014	0.1701	16	0.0001
Mysql Total
Database connection	0.0007	0.0908	1	0.0007
Mysqli_queries	0.7506	92.9689	63	0.0119
Looping result	0.0007	0.0831	61	0.0000
Template Total	0.7763	96.2	2	0.3882
Template load	0.0019	0.2314	2	0.0009
Template processing	0.7745	95.9264	2	0.3872
Template load and register function	0.0002	0.0212	1	0.0002
states
state_id_array	0.0009	0.1086	1	0.0009
state_identifier_array	0.0016	0.1986	2	0.0008
Override
Cache load	0.0016	0.1997	33	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0012	0.1521	2	0.0006
Fetch class attribute name	0.0028	0.3456	6	0.0005
XML
Image XML parsing	0.0023	0.2823	2	0.0011
class_abstraction
Instantiating content class attribute	0.0000	0.0019	8	0.0000
General
dbfile	0.0031	0.3870	16	0.0002
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
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
8	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
2	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: 21 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs