example.sites.php

  1. drupal
    1. 7 sites/example.sites.php
    2. 8 sites/example.sites.php

Configuration file for Drupal's multi-site directory aliasing feature.

Drupal searches for an appropriate configuration directory based on the website's hostname and pathname. A detailed description of the rules for discovering the configuration directory can be found in the comment documentation in 'sites/default/default.settings.php'.

This file allows you to define a set of aliases that map hostnames and pathnames to configuration directories. These aliases are loaded prior to scanning for directories, and they are exempt from the normal discovery rules. The aliases are defined in an associative array named $sites, which should look similar to the following:

$sites = array( 'devexample.com' => 'example.com', 'localhost.example' => 'example.com', );

The above array will cause Drupal to look for a directory named "example.com" in the sites directory whenever a request comes from "example.com", "devexample.com", or "localhost/example". That is useful on development servers, where the domain name may not be the same as the domain of the live server. Since Drupal stores file paths into the database (files, system table, etc.) this will ensure the paths are correct while accessed on development servers.

To use this file, copy and rename it such that its path plus filename is 'sites/sites.php'. If you don't need to use multi-site directory aliasing, then you can safely ignore this file, and Drupal will ignore it too.

File

sites/example.sites.php
View source
  1. <?php
  2. /**
  3. * @file
  4. * Configuration file for Drupal's multi-site directory aliasing feature.
  5. *
  6. * Drupal searches for an appropriate configuration directory based on the
  7. * website's hostname and pathname. A detailed description of the rules for
  8. * discovering the configuration directory can be found in the comment
  9. * documentation in 'sites/default/default.settings.php'.
  10. *
  11. * This file allows you to define a set of aliases that map hostnames and
  12. * pathnames to configuration directories. These aliases are loaded prior to
  13. * scanning for directories, and they are exempt from the normal discovery
  14. * rules. The aliases are defined in an associative array named $sites, which
  15. * should look similar to the following:
  16. *
  17. * $sites = array(
  18. * 'devexample.com' => 'example.com',
  19. * 'localhost.example' => 'example.com',
  20. * );
  21. *
  22. * The above array will cause Drupal to look for a directory named
  23. * "example.com" in the sites directory whenever a request comes from
  24. * "example.com", "devexample.com", or "localhost/example". That is useful
  25. * on development servers, where the domain name may not be the same as the
  26. * domain of the live server. Since Drupal stores file paths into the database
  27. * (files, system table, etc.) this will ensure the paths are correct while
  28. * accessed on development servers.
  29. *
  30. * To use this file, copy and rename it such that its path plus filename is
  31. * 'sites/sites.php'. If you don't need to use multi-site directory aliasing,
  32. * then you can safely ignore this file, and Drupal will ignore it too.
  33. */
  34. /**
  35. * Multi-site directory aliasing:
  36. *
  37. * Edit the lines below to define directory aliases. Remove the leading hash
  38. * signs to enable.
  39. */
  40. # $sites['devexample.com'] = 'example.com';
  41. # $sites['localhost.example'] = 'example.com';
Login or register to post comments