Multisite config

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
mikle mikle	Friday 16 May 2003 1:39:01 am Hay, i setting up two sites in one Ez Publish installation (which was quite simple and well explained, thanks to Bard). I consern about cache files and storage filder (generaly about whole 'var' folder ) - should i make them seprate for the sites? At the moment they are the same and i don't see any problems... What is your recomendation?
Jo Henrik Endrerud	Friday 16 May 2003 2:55:11 am I don't see any problems that could occur by using the same var on several sites (at least not as long both sites are using the same database). Jo Henrik Endrerud \| System Developer @ Seeds Consulting \| http://www.seeds.no
Maggie Martin	Friday 16 May 2003 3:09:27 pm what if they are using separate databases? M.
Jo Henrik Endrerud	Sunday 18 May 2003 10:28:40 am I'm not sure what would happen, but I will recomend you to have separate var directories if you have different databases. Jo Henrik Endrerud \| System Developer @ Seeds Consulting \| http://www.seeds.no
Joel Finkel	Sunday 18 May 2003 2:32:02 pm I can see that in the var/cache/content directory you can easily create a new directory for the new site. I assume the system will automatically use this for caching the new site. It is easy to copy the entire var directory and make a new one for the new site, but where would one establish the setting that would tell the system that this new site is to use this entirely new directory?
Jeroen van Gorkum	Sunday 18 May 2003 3:53:06 pm > but where would one establish the setting that would tell the system > that this new site is to use this entirely new directory? these settings are described here: Multi site configuration, http://ez.no/manual/install/multisite i'm using one ezp installation for multiple sites, with multiple databases, and this works AFAICT. mind though that modfix.sh and clearcache.sh ignore these new directories in var/; you'll have to do those tasks manually. you'll also have to create the new storage/* tree(s) yourself. hth, jeroen.

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

Main resources:

Total runtime	0.0165 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	587.9141	152.6250
Module start 'layout'	0.0051	0.0038	740.5391	39.4453
Module start 'content'	0.0089	0.0058	779.9844	93.2266
Module end 'content'	0.0146	0.0019	873.2109	34.3047
Script end	0.0165		907.5156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	16.3984	14	0.0002
Check MTime	0.0012	7.0887	14	0.0001
Mysql Total
Database connection	0.0005	3.1340	1	0.0005
Mysqli_queries	0.0028	16.8643	3	0.0009
Looping result	0.0000	0.1572	1	0.0000
Template Total	0.0014	8.6	1	0.0014
Template load	0.0007	4.3729	1	0.0007
Template processing	0.0007	4.1739	1	0.0007
Override
Cache load	0.0005	2.9523	1	0.0005
General
dbfile	0.0003	1.9586	8	0.0000
String conversion	0.0000	0.0620	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