Book Image

Drupal 7 Multi Sites Configuration

Book Image

Drupal 7 Multi Sites Configuration

Overview of this book

Drupal is one of the most powerful PHP Content Management Systems there is. However, why would you install a CMS for every site you build? With just one copy of Drupal you can host several sites. Drupal has long had multi-site support, and Drupal 7's support is even better than previous versions. Drupal 7 Multi-Sites Configuration will teach you how to host several websites on a single copy of Drupal. You will learn how to create different sites, each with its own domain, content, and theme. This valuable information will help you to save time by managing modules and sharing them across several sites as well as administering your sites all in one place.This book will show you how to configure a system for multi-site, and then install several sites on one copy of Drupal, all with their own domain name and database. Learn how to install and share modules and themes, configure Apache, PHP, and MySQL for multi-site, and then manage the site. Once your site system is successfully set up, discover some of the advanced configurations possible with Drupal multi-site, as well as how to upgrade and maintain your sites.
Table of Contents (11 chapters)

Summary


In this chapter we looked at how each site could be configured. We started out by looking at site settings, and saw how they are separate by default, but can be shared to a limited extent. Then we moved on to modules and themes. We saw that in a multi-site configuration, modules and themes can be shared, or they can be stored in just one site. We also saw how even shared modules can have different configurations on different sites. We looked at themes, focusing on the complications that arise between the tight coupling of a site's database data and its theme files. We looked at using site-specific subthemes, focusing on how that could mitigate the problem.

In the next chapter we are going to turn our attention to site administration. There, we will see once again how sharing code, but not database data, can introduce some subtle challenges.