Skip to content
Snippets Groups Projects
Select Git revision
  • 3b3a6d794454123f2778641b19f51bf56cbafc56
  • develop default
  • issue-525
  • topics/add-contribution-info
  • master
  • master-no-logins
  • issue-424
  • svn-trunk
  • svn-staging
  • svn-testing
  • 7.6.1
  • 7.6
  • 7.5.1
  • 7.5
  • 7.4
  • 7.3.1
  • 7.3
  • 7.2
  • 7.1
  • 2012-04-18
  • 2012-04-03
  • 2012-04-02
  • 2012-03-01
  • 2012-02-07
  • 20120207
  • 2012-01-13
  • 2012-01-12
  • 2011-12-16
  • 2011-12-05
  • 2011-11-17
30 results

example.sites.php

Blame
  • Forked from UNL Information Services / UNL-CMS
    804 commits behind the upstream repository.
    user avatar
    Tim Steiner authored
    git-svn-id: file:///tmp/wdn_thm_drupal/branches/drupal-7.x@58 20a16fea-79d4-4915-8869-1ea9d5ebf173
    9de53ac8
    History
    example.sites.php 1.81 KiB
    <?php
    // $Id: example.sites.php,v 1.3 2010/04/15 12:01:28 dries Exp $
    
    /**
     * @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['devexample.com'] = 'example.com';
    # $sites['localhost.example'] = 'example.com';