Design/Database dilemna

Next topic

Author	Message
Shurbann Martes	Friday 12 December 2003 11:04:27 am Hello eZ, I have an intranet growing and becoming larger, so I want to split this into two intranet that share some information they have in common. But they should have their onw look and feel. What should I do? - Let them us their own database? disadvantage (I think): I can't share the information they have in common. Just by writing one article for example or - put them in one database? disadvantage (I think): If someone change the design (design_A to design_B) in the url they will see the information of intanet A using design of/look of intranet B. I'm hoping that you will discuss these issues here so I will have an idea what to do. Greets, Shurbann
Alex Jones	Friday 12 December 2003 11:28:02 am I would recommend that you use a single database/install of eZ publish. As you mentioned, this will allow you to save content and will use less resources than two installations of eZ publish. Is it really a big deal if someone hacks the URL and sees the same information in a different design? If you set these up as separate subdomains (intranet.yourcompany.com & internal.yourcompany.com) it is less likely that people will think to change the URL compared to intranet.yourcompany.com/design/ If it is a big deal, you can look at limiting access to each one via a password, IP subnet or the like. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>

Author

Message

Friday 12 December 2003 11:04:27 am

Hello eZ,

I have an intranet growing and becoming larger, so I want to split this into two intranet that share some information they have in common.

But they should have their onw look and feel.
What should I do?

- Let them us their own database?
disadvantage (I think): I can't share the information they have in common. Just by writing one article for example

- put them in one database?
disadvantage (I think): If someone change the design (design_A to design_B) in the url they will see the information of intanet A using design of/look of intranet B.

I'm hoping that you will discuss these issues here so I will have an idea what to do.

Greets,
Shurbann

Alex Jones

Friday 12 December 2003 11:28:02 am

I would recommend that you use a single database/install of eZ publish. As you mentioned, this will allow you to save content and will use less resources than two installations of eZ publish.

Is it really a big deal if someone hacks the URL and sees the same information in a different design? If you set these up as separate subdomains (intranet.yourcompany.com & internal.yourcompany.com) it is less likely that people will think to change the URL compared to intranet.yourcompany.com/design/ If it is a big deal, you can look at limiting access to each one via a password, IP subnet or the like.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

eZ debug

Timing:	Jan 18 2025 22:33:02
Script start
Timing:	Jan 18 2025 22:33:02
Module start 'layout'
Timing:	Jan 18 2025 22:33:02
Module start 'content'
Timing:	Jan 18 2025 22:33:03
Module end 'content'
Timing:	Jan 18 2025 22:33:03
Script end

Main resources:

Total runtime	0.9056 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	587.8828	152.6094
Module start 'layout'	0.0059	0.0028	740.4922	39.4141
Module start 'content'	0.0086	0.8955	779.9063	523.9688
Module end 'content'	0.9041	0.0014	1,303.8750	8.1875
Script end	0.9055		1,312.0625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3544	16	0.0002
Check MTime	0.0013	0.1435	16	0.0001
Mysql Total
Database connection	0.0009	0.1043	1	0.0009
Mysqli_queries	0.8570	94.6412	54	0.0159
Looping result	0.0005	0.0535	52	0.0000
Template Total	0.8736	96.5	2	0.4368
Template load	0.0022	0.2393	2	0.0011
Template processing	0.8714	96.2322	2	0.4357
Template load and register function	0.0002	0.0174	1	0.0002
states
state_id_array	0.0007	0.0782	1	0.0007
state_identifier_array	0.0009	0.0982	2	0.0004
Override
Cache load	0.0017	0.1911	20	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0601	2	0.0003
Fetch class attribute name	0.0009	0.1027	3	0.0003
XML
Image XML parsing	0.0006	0.0682	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0008	3	0.0000
General
dbfile	0.0008	0.0877	16	0.0000
String conversion	0.0000	0.0009	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs