Some multi cms questions

Permalink
I have a few questions about multi-cms:
I understand that with multi-cms installation most of the concrete5 source code will be in a shared webmap and every new website will be installed with a new subdomain.

But what about the database(s)? Is there for every new site also a new database with tables or is there 1 big shared database for all mult-cms sites?
If there is not a shared database – can anyone tell me something (experiences) about the process to update/upgrade over 300 sites (especially the >300 databases)

If I create a new functionality for all the websites, is it possible to add this in the shared webserver sourcemap and make it available for all websites?
Thanks a lot for any answer.

lkmd
 
ThemeGuru replied on at Permalink Reply
ThemeGuru
Well the nice thing about c5 is the centralized core. Which means one core for all your c5 installs (you'll be needing some hosting docs. Might I suggest turning to the hosting partnership or else if your still stuck I've setup some a centralized core on my own shared host.)

Well it probably be best to have 1 database per install.

Upgrading isnt that hard. If your really concerned on your experience you might want the Multi-Site Manager for WHM. (A cpanel addon) It's released with a annual subscription from c5.

I'm assuming that your created functionality is like a package (addon/block/theme) you would need to upload it to the packages folder on each site. Or else if you really wanted maybe look at the core and hack it a little so your package will always be installed.

Hope that helps

-TG