By wqr786 on

I want to run multiple sites using 1 Drupal. I want to share multiple modules, for example, Site A should run Module A1, Module A2, Module B1, where as Site B will run only Module B1.

Also I want multiple themes for all those sites, Site A to run different theme, Site B to run different theme.

And also those sites to be on different subdomains:
siteA.mysite.com
siteB.mysite.com

Is it possible, please let me know? because I'm thinking of either 2 things to use for this, either CakePHP or Drupal. Which

Thanks
Waqar

⋅ Categories: Drupal 6.x

Comments

zbricoleur’s picture

zbricoleur commented

Yes, quite possible. The basic instructions on how to do it are in INSTALL.txt.

scoutbaker’s picture

scoutbaker commented

That sounds like a multi-site setup.

There's lots of documentation available by clicking on the Documentation tab at the top of the page.

wqr786’s picture

wqr786 commented

Thanks Drupal Community

Just wanted to confirm, if I run multiple sites such as SITE A and SITE B, will the following be possible:

SITE A configurations:
Module A installed
Module B installed
Module C installed
Users
Theme A installed

SITE B configurations:
Module A installed
Module C installed
Module B Not installed
Users are different from SITE A
Theme B installed

I hope the scenario helps understand my requirement. I'm a drupal user, developer, and also we develop projects in drupal, but for this project I just want to be 100% sure before I plan to use it or any other framework that best suits the requirements.

If someone can suggest me Advantages and Disadvantages of such scenario with drupal, I would really appreciate as well.

Thanks
Waqar

zbricoleur’s picture

zbricoleur commented

Use different databases for the two sites; that keeps the two user bases (and content) separate. But both sites will be able to "see" and use any modules you put in sites/all/modules. You can enable/disable modules at will, on a per-site basis, in the admin area of each site. Additionally, if you don't want site A to even have the option of using module C (for instance), you can put module C in sites/siteB/modules, and site A will not be able to see it.

The advantage is that you only have one codebase to maintain. That is also a disadvantage, in that when you want to upgrade one site, you must upgrade them all. But on the whole, much better than the headaches of maintaining multiple code bases. There are no performance trade-offs that I'm aware of.

wqr786’s picture

wqr786 commented

Thank you very much, your post has given me satisfaction on my choice: DRUPAL :-)