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