drupal/sites/default.sites.php

<?php
// $Id$

/**
 * @file
 * 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.
 */

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