Forums / General / Design/Database dilemna

Design/Database dilemna

Previous topic

General

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

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

- 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>