Single Database, Single Publish Domain, Multiple Client Domains

Next topic

Author	Message
Kevin Landers	Friday 05 December 2003 2:35:28 pm Hey guys, Forgive me if I have missed something in another post previous to this posting. Exams and lack of sleep aren't exactly helping me in understanding this product. Here is what I would like to do: I would like to implement a single Postgres database for all eZ-publish sites. I would like to offer a http://publish.bezaleel.net domain that all my clients could login to with their username and password and gain access to only their content, templates, etc. I would want them to have complete access to THIER site, but not any access to anyother client's website information. From this database, I would like each client to have their own full domain name. www.whatever.com I would like for this domain not to have to have all the eZ-publish install files sitting around in the httproot directory. I would prefer to use this so that updating eZpublish would be simplistic and spontaeneous. I do not care whether a client did not wish to upgrade, they would all upgrade. Another note is that we have our own server and do NOT use virtual hosting, instead we assign each domain an IP number. I am not sure whether this will affect eZ-publish in any way. Well, I would simply ask for your guidance and direction in determining whether eZ-publish will accomplish the above or not. And if not, are there any suggestions to software that will support the above requests? All help is appreciated! Kevin L.
Marco Zinn	Saturday 13 December 2003 11:33:07 am Hi Kevin, i didn't do this, but ez3 was designed to do a lot of this. You can have multiple VHosts (or IPs, in your case) be handled by one single ezPublish installation (the files are there just once). Then you will need to create at least two siteaccesses for each customer (one for "user", one for "admin"). I would suggest one unique MySQL DB per customer, which those two siteaccesses will use. Then, you will probably need one "Design" per customer (or two, if you want to allow them to change the admin Design). "Design" will be assigned to the siteaccess, too and will take care of the Templates. This should get you going more or less. Notes: - I don't know, if anyone tried this yet - I'm not sure, if/how you can permit the customers to change Designs, which are not theirs, especially the "Standard" Design, which is the fallback for everyone - Maybe it's even possible to use just one "big" MySQL, but i would not recommend this at all. See the documentation about "siteaccesses" to give you some more background info and let's hope, that someone already did, what you want to do (you wish is not so extraordinary ;) ) PS: Sorry, I'm using MySQL. Read "Postgres" ;) Marco http://www.hyperroad-design.com
Kjell Andersen	Thursday 08 January 2004 5:21:44 am Hi, Kevin If I understood your problem right I just did more or less what you wanted to do. I have two different domains using the same db (MySQL) but with different designs. I use Virtual hosting, but everything else seems quite similar. What did I do: Create a design directory for each site, just like the doc. tells you. In the settings/siteaccess you create a "site" and "site_admin" directory for each site and you just specify the same db in each site.ini.append file. In settings/override i modified the the "site.ini.append.php" file to [SiteSettings] DefaultAccess=site1 SiteList[]=site1 SiteList[]=site2 [SiteAccessSettings] CheckValidity=false MatchOrder=host HostMatchType=map HostMatchMapItems[]=www.site1.com;site1 HostMatchMapItems[]=admin.site1.net;site1_admin HostMatchMapItems[]=www.site2.com;site2 HostMatchMapItems[]=admin.site2.org;site2_admin The you just have to create forlders, sections and usergroups for each site and give limited access to each site administrator. Kjell

Author

Message

Friday 05 December 2003 2:35:28 pm

Hey guys,

Forgive me if I have missed something in another post previous to this posting. Exams and lack of sleep aren't exactly helping me in understanding this product.

Here is what I would like to do:

I would like to implement a single Postgres database for all eZ-publish sites.

I would like to offer a http://publish.bezaleel.net domain that all my clients could login to with their username and password and gain access to only their content, templates, etc. I would want them to have complete access to THIER site, but not any access to anyother client's website information.

From this database, I would like each client to have their own full domain name. www.whatever.com
I would like for this domain not to have to have all the eZ-publish install files sitting around in the httproot directory. I would prefer to use this so that updating eZpublish would be simplistic and spontaeneous. I do not care whether a client did not wish to upgrade, they would all upgrade.

Another note is that we have our own server and do NOT use virtual hosting, instead we assign each domain an IP number. I am not sure whether this will affect eZ-publish in any way.

Well, I would simply ask for your guidance and direction in determining whether eZ-publish will accomplish the above or not.

And if not, are there any suggestions to software that will support the above requests?

All help is appreciated!

Kevin L.

Marco Zinn

Saturday 13 December 2003 11:33:07 am

Hi Kevin,
i didn't do this, but ez3 was designed to do a lot of this.
You can have multiple VHosts (or IPs, in your case) be handled by one single ezPublish installation (the files are there just once).
Then you will need to create at least two siteaccesses for each customer (one for "user", one for "admin").
I would suggest one unique MySQL DB per customer, which those two siteaccesses will use.
Then, you will probably need one "Design" per customer (or two, if you want to allow them to change the admin Design). "Design" will be assigned to the siteaccess, too and will take care of the Templates.
This should get you going more or less.

Notes:
- I don't know, if anyone tried this yet
- I'm not sure, if/how you can permit the customers to change Designs, which are not theirs, especially the "Standard" Design, which is the fallback for everyone
- Maybe it's even possible to use just one "big" MySQL, but i would not recommend this at all.

See the documentation about "siteaccesses" to give you some more background info and let's hope, that someone already did, what you want to do (you wish is not so extraordinary ;) )

PS: Sorry, I'm using MySQL. Read "Postgres" ;)

Marco
http://www.hyperroad-design.com

Kjell Andersen

Thursday 08 January 2004 5:21:44 am

Hi, Kevin
If I understood your problem right I just did more or less what you wanted to do.

I have two different domains using the same db (MySQL) but with different designs. I use Virtual hosting, but everything else seems quite similar.

What did I do:

Create a design directory for each site, just like the doc. tells you.

In the settings/siteaccess you create a "site" and "site_admin" directory for each site and you just specify the same db in each site.ini.append file.

In settings/override i modified the the "site.ini.append.php" file to

[SiteSettings]
DefaultAccess=site1
SiteList[]=site1
SiteList[]=site2

[SiteAccessSettings]
CheckValidity=false

MatchOrder=host
HostMatchType=map

HostMatchMapItems[]=www.site1.com;site1
HostMatchMapItems[]=admin.site1.net;site1_admin
HostMatchMapItems[]=www.site2.com;site2
HostMatchMapItems[]=admin.site2.org;site2_admin

The you just have to create forlders, sections and usergroups for each site and give limited access to each site administrator.

Kjell

eZ debug

Timing:	Jan 19 2025 04:37:40
Script start
Timing:	Jan 19 2025 04:37:41
Module start 'layout'
Timing:	Jan 19 2025 04:37:41
Module start 'content'
Timing:	Jan 19 2025 04:37:41
Module end 'content'
Timing:	Jan 19 2025 04:37:41
Script end

Main resources:

Total runtime	0.9944 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	590.7734	152.6875
Module start 'layout'	0.0057	0.0029	743.4609	39.5234
Module start 'content'	0.0087	0.9845	782.9844	583.0625
Module end 'content'	0.9932	0.0012	1,366.0469	12.0781
Script end	0.9944		1,378.1250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.3412	16	0.0002
Check MTime	0.0014	0.1422	16	0.0001
Mysql Total
Database connection	0.0008	0.0770	1	0.0008
Mysqli_queries	0.9363	94.1519	59	0.0159
Looping result	0.0006	0.0641	57	0.0000
Template Total	0.9593	96.5	2	0.4797
Template load	0.0020	0.2033	2	0.0010
Template processing	0.9573	96.2646	2	0.4786
Template load and register function	0.0002	0.0231	1	0.0002
states
state_id_array	0.0016	0.1648	1	0.0016
state_identifier_array	0.0016	0.1623	2	0.0008
Override
Cache load	0.0017	0.1732	52	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0906	3	0.0003
Fetch class attribute name	0.0014	0.1419	4	0.0004
XML
Image XML parsing	0.0008	0.0782	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0015	4	0.0000
General
dbfile	0.0008	0.0763	16	0.0000
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/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
9	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
8	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: 23 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs