Thread

Actually, Drupal can do something like this. You can run a single code base with site-specific modules, themes, and whatnot; each site can use its own database or share a database with a different table prefix (and you can mix and match). On the database side, if you know what you’re doing you can even share individual tables between sites.

I don’t know that I would recommend Drupal for an all eggs in one basket setup if the individual sites are for clients, though. Before switching to EE, I used to run my sites as described above (shared code with site-specific add-ons, individual databases) and it’s debatable how well this setup scales. Any updates to Drupal core have to happen at the same time, which is fine for a couple, but not so fine for many tens and up. And not to forget the pain of major version upgrades.

Hi Markus,

I just gave Drupal a spin today and amazed how easy it is to setup multi sites without any add-on and is quite flexible like you said.  Hope one day EE has something like that.  I also agree with you that “all eggs in one basket” approach may not be a good choice but look like that’s how our management will stick to.

Arnold

Sharing the database between unrelated sites for different clients poses a real privacy and data-protection problem. If Arnold were coming from the European Union I think it would be definitely be illegal, based on the kinds of questions we see coming from EU-based clients. I don’t know enough about the Canadian law even to have a base opinion, but there may be legal issues for Arnold’s management to consider.

I’m closing this thread for two reasons. Arnold has found a solution that works for him and the thread venturing beyond the scope of his original question.