By mattyoung on
Right now I have each site as a separate Drupal install. I want to have just one Drupal install and serve multiple sites out of that. Where can I find documentation on how to do this?
Right now I have each site as a separate Drupal install. I want to have just one Drupal install and serve multiple sites out of that. Where can I find documentation on how to do this?
Comments
Here...
http://drupal.org/node/43816
The Drupal search feature and Google are your friends.
There is a lot of
There is a lot of documentation under http://drupal.org/node/43816 (some pages better than other), and also in Drupal's INSTALL.txt file.
The big picture is this:
1. Make all your different site domains or subdomains point to the same Drupal installation directory, and not to their own different directories. This way, drupal will be able to handle all site requests. For example:
http://www.site1.com --> /home/[blah]/public_http
http://site2.com --> /home/[blah]/public_http
http://sub.site1.com --> /home/[blah]/public_http (*not* public_http/sub)
http://site2.com/sub --> /home/[blah]/public_http (*not* public_http/sub)
Depending on what you want to do and what your hosting plan allows, this can be done either in cpanel or in apache configuration with vhosts or aliases, or with unix symlinks. It *can't* be done with apache redirects or rewrites, because the request URL must be preserved.
2. Under the sites/ directory, create subdirectories properly named. In the above cases, for example:
sites/site1.com
sites/site2.com
sites/sub.site1.com
sites/site1.com.sub
In each of these directories, copy the settings.php file of one of your sites.
Drupal will compare any URL requests with the names of these directories and will bring up the right site. If it finds no match, it will go to the sites/default site (if there is a settings.php file there).
3. Any modules and themes which you place under sites/all/modules and sites/all/themes will be available to all sites. Any modules and themes which you place under sites/site-name/modules and sites/site-name/themes will be available only to the specific site.
After doing this, you may need to visits each site's admin/build/modules page once, to have the paths of the modules and themes automatically updated. You may also need to update the settings of your files/images directories.
Got to flip to a built-in theme...
...before moving the active theme from 'sites/all/themes' to 'sites/www.mysite.com/themes'. I got blank screen. So I switch to Garland first, move the my theme, then re-enable.
Here is a write up I did a
Here is a write up I did a few weeks back for multisites on Plesk. Same principal, as outlined eloquently by cog.rusty, applies.
http://drupal.org/node/335997
----------------------------------------------------------------------
http://classicvinyl.biz
http://music.bwv810.com
http://association.drupal.org/user/1207