It is possible to have one ez source installation and a lot of different sites ( db's ) with different siteaccesses.
We do this for our own projects. We put all projektrelated stuff (design, siteaccess) which point to one db in a single ez extension called site_projectname. So we have a good handling.
e.g we have an installation with 38 different sites ( ez4.0.1 with lighttpd and php fastcgi ). We did some small ez patches to have a better handling of this type of installation.
It is also possible to have one ez db with different domains and sets of users. For this you have to create different contentstructures and roles.
Thank you for your answer. I have been looking for the site_projectname extension you have mentionned and all I could find is this discussion : http://ez.no/br/developer/forum/suggestions/ini_priority_vs_extension_settings/(offset)/20
It leads to a not-yet-integrated lookalike patch : http://issues.ez.no/IssueView.php?Id=13382&activeItem=1
Is this what you were refering to? If it is, is there any documentation explaining how to configure it?
I must confess I am a bit unconfortable with using an unintegrated patch, is there any alternative solution to this problem?
you do not need to patch ez. But the patches makes it much easear to keep control over the different settings.
you can still do the following, but siteaccesses + designs in an ezextension. You have to care about global ini settings.
extension
- site_projectname
- design
- yourdesign
- settings
- siteAccess1
site.ini.append.php ( put here all sitaccessrelated stuff )
- sieAccess2
site.ini.append.php ( site_projectname/settings/site.ini.append.php => this settings are used for all site_extensions - only put here information about HostMatchItems ... )
...
settings
- override
site.ini.append.php ( ActiveExtensions[]=site_projectname )
