This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » Setup & design » Site Infrastructure
expandshrink

Site Infrastructure

Site Infrastructure

Tuesday 06 November 2012 9:53:29 pm - 3 replies

Hi there,

I am working for a company where we use ezp extensively. We have around 70 sites built on ezp. Currently we have all these sites sitting in one installation of ezp (Multisite setup). We use deployment scripts to deploy and update sites. 

We also have extension repository that these sites depend on. (Not all sites need all the extensions...but they are available if they do need them)

Problem we are having, because an extension can be used by any Site A and Site B in the list of 70, updating an extension with this setup for just Site A is proving to be impossible.

I was wondering if any of the users in the community is using this sort of setup and have any ideas in improving the infrastructure.

Just to give you an idea, the setup we have is

Ezp core

/var/www/ezpublish_core

All our sites sit in

/var/www/ezpublish_core/extension/site1/var/www/ezpublish_core/extension/site70

All our extensions also sit in

/var/www/ezpublish_core/extension/ext_1/var/www/ezpublish_core/extension/ext_2/var/www/ezpublish_core/extension/ext_100

Looking for better infrastructure
Cheers

Raghu

Wednesday 07 November 2012 10:26:29 am

Why not name extensions according to their version?

eg: my_ext_1_1, my_ext_1_2

Note: this has the disadvantage that you need to alter all the ini files within the extension where the extension name is present.

Or you could use separate ez installations for the different customers, and use symlink to share most files:

- have every site use one physical, different root directory

- share the whole kernel, design directories between all sites, by using symlinks (/var/www/site1/kernel => /var/ez_core/kernel)

- share versioned extensions using symlinks (var/www/site1/extension/myext => /var/ez_core/extension/myext_1.1)

This allows you not only to upgrade extensions but also ez, separately for every site.

The downside is that cache files will be generated fully for every site (you might be sharing caches just a bit more now).

Other benefits: you get separate logs for every site

Wednesday 07 November 2012 10:27:50 am

ps: teh above answer is for the different-extension-versions-on-different-sites problem.

to have an extension enabled only on one (or more) siteaccess is easy: just use the siteaccessextension setting

Friday 09 November 2012 3:42:17 am

Thanks Gaetano, i will put fwd the plan and see what my peers think of it happy.gif Emoticon.....appreciate the suggestions!

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from