Your SlideShare is downloading. ×
  • Like
Drupal Multi-Site Setup
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Drupal Multi-Site Setup


Slides from a presentation I did on Multi-Site Setups in Drupal at the Jamaica Drupal Group on June 20, 2009

Slides from a presentation I did on Multi-Site Setups in Drupal at the Jamaica Drupal Group on June 20, 2009

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here

    Here is requirements for certain Multisite.

    Want to choose best way to satisfy these requirements.

    So Can you tell me what is the best? Aegir, Spaces, Usual Domain Access multisite system, OpenAtrium, Organic Group?
    Are you sure you want to
    Your message goes here
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Drupal Multi-Site Setup
  • 2. Yannick Lyn Fatt axle_foley00 on Who am I?
  • 3. Where do I work? The University of the West Indies at Mona, Jamaica
  • 4. What's a Multi-Site?
  • 5.
      Using one install (or codebase) of Drupal but having more than one site use that same codebase.
  • 6. Single Codebase
  • 7. Multi-Site Structure
  • 8. What's the alternative?
  • 9.
      Running separate installations of Drupal for each site.
  • 10. Separate Installations Site 1 Site 2
  • 11. Advantages
    • Shared codebase means all sites are using the same version.
    • 12. One big upgrade of drupal core can be done as opposed to updating the core code for separate installations each of which could be a different version of Drupal.
    • 13. Modules/Themes can be shared across sites or they can have their own modules/themes.
  • 14. Disadvantages
    • Updating Drupal core means all sites need to be put offline for the update.
    • 15. Updating core and contrib modules, means running update.php for each site in your Multi-Site setup. (though you might be able to use Aegir/Drush to run update.php for all sites in one go)
  • 16. How does Drupal determine which site to load?
  • 17. For example, for a fictitious site installed at, the 'settings.php' is searched in the following directories: 1. sites/ 2. sites/ 3. sites/org.mysite.test 4. sites/ 5. sites/ 6. sites/org.mysite 7. sites/ 8. sites/ 9. sites/org 10. sites/default
  • 18. How to handle the database(s)?
    • Two options
      • One database with different prefixed tables.
      • 19. Separate databases for each site in the Multi-site.
    • Which is better?
      • It's up to you and the resources available to you. We chose separate databases.
  • 20. Quick Demo
  • 21. Helpful Tips
    • Write an Installation Profile(s)
      • HOWTO: Write an Installation Profile -
      • 22. Profile Generator -
      • 23. Install Profile API -
    • Write some scripts for common tasks
      • Drush/Aegir might be able to do some of this already
  • 24. Helpful Tips
    • Set some conventions and follow them.
      • e.g. databases are named by the 'sitename' and users created for each database with the name 'sitename_user'.
  • 25. Resources
    • Run Multiple Sites from a single code base -
    • 26. Multi-Site Group -
    • 27. Multi-Site Installation and Setup Links -
    • 28. How To: Multisites vs. Multiple Sites -
  • 29. Resources
    • Sharing Users and content across multiple sites -
    • 30. Drush -
    • 31. Aegir -
  • 32. Questions?
  • 33. Thanks for listening! Have a nice Day! :)