Mercurial > defr > drupal > core

annotate sites/default/default.settings.php @ 20:e3d20ebd63d1 tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added tag 6.9 for changeset 3edae6ecd6c6
author Franck Deroche <franck@defr.org>
date Thu, 15 Jan 2009 10:16:10 +0100
parents acef7ccb09b5
children
rev   line source
webmaster@1 1 <?php
webmaster@9 2 // $Id: default.settings.php,v 1.8.2.1 2008/08/13 06:52:36 dries Exp $
webmaster@1 3
webmaster@1 4 /**
webmaster@1 5 * @file
webmaster@1 6 * Drupal site-specific configuration file.
webmaster@1 7 *
webmaster@1 8 * IMPORTANT NOTE:
webmaster@1 9 * This file may have been set to read-only by the Drupal installation
webmaster@1 10 * program. If you make changes to this file, be sure to protect it again
webmaster@1 11 * after making your modifications. Failure to remove write permissions
webmaster@1 12 * to this file is a security risk.
webmaster@1 13 *
webmaster@1 14 * The configuration file to be loaded is based upon the rules below.
webmaster@1 15 *
webmaster@1 16 * The configuration directory will be discovered by stripping the
webmaster@1 17 * website's hostname from left to right and pathname from right to
webmaster@1 18 * left. The first configuration file found will be used and any
webmaster@1 19 * others will be ignored. If no other configuration file is found
webmaster@1 20 * then the default configuration file at 'sites/default' will be used.
webmaster@1 21 *
webmaster@1 22 * For example, for a fictitious site installed at
webmaster@1 23 * http://www.drupal.org/mysite/test/, the 'settings.php'
webmaster@1 24 * is searched in the following directories:
webmaster@1 25 *
webmaster@1 26 * 1. sites/www.drupal.org.mysite.test
webmaster@1 27 * 2. sites/drupal.org.mysite.test
webmaster@1 28 * 3. sites/org.mysite.test
webmaster@1 29 *
webmaster@1 30 * 4. sites/www.drupal.org.mysite
webmaster@1 31 * 5. sites/drupal.org.mysite
webmaster@1 32 * 6. sites/org.mysite
webmaster@1 33 *
webmaster@1 34 * 7. sites/www.drupal.org
webmaster@1 35 * 8. sites/drupal.org
webmaster@1 36 * 9. sites/org
webmaster@1 37 *
webmaster@1 38 * 10. sites/default
webmaster@1 39 *
webmaster@1 40 * If you are installing on a non-standard port number, prefix the
webmaster@1 41 * hostname with that number. For example,
webmaster@1 42 * http://www.drupal.org:8080/mysite/test/ could be loaded from
webmaster@1 43 * sites/8080.www.drupal.org.mysite.test/.
webmaster@1 44 */
webmaster@1 45
webmaster@1 46 /**
webmaster@1 47 * Database settings:
webmaster@1 48 *
webmaster@1 49 * Note that the $db_url variable gets parsed using PHP's built-in
webmaster@1 50 * URL parser (i.e. using the "parse_url()" function) so make sure
webmaster@1 51 * not to confuse the parser. If your username, password
webmaster@1 52 * or database name contain characters used to delineate
webmaster@1 53 * $db_url parts, you can escape them via URI hex encodings:
webmaster@1 54 *
webmaster@1 55 * : = %3a / = %2f @ = %40
webmaster@1 56 * + = %2b ( = %28 ) = %29
webmaster@1 57 * ? = %3f = = %3d & = %26
webmaster@1 58 *
webmaster@1 59 * To specify multiple connections to be used in your site (i.e. for
webmaster@1 60 * complex custom modules) you can also specify an associative array
webmaster@1 61 * of $db_url variables with the 'default' element used until otherwise
webmaster@1 62 * requested.
webmaster@1 63 *
webmaster@1 64 * You can optionally set prefixes for some or all database table names
webmaster@1 65 * by using the $db_prefix setting. If a prefix is specified, the table
webmaster@1 66 * name will be prepended with its value. Be sure to use valid database
webmaster@1 67 * characters only, usually alphanumeric and underscore. If no prefixes
webmaster@1 68 * are desired, leave it as an empty string ''.
webmaster@1 69 *
webmaster@1 70 * To have all database names prefixed, set $db_prefix as a string:
webmaster@1 71 *
webmaster@1 72 * $db_prefix = 'main_';
webmaster@1 73 *
webmaster@1 74 * To provide prefixes for specific tables, set $db_prefix as an array.
webmaster@1 75 * The array's keys are the table names and the values are the prefixes.
webmaster@1 76 * The 'default' element holds the prefix for any tables not specified
webmaster@1 77 * elsewhere in the array. Example:
webmaster@1 78 *
webmaster@1 79 * $db_prefix = array(
webmaster@1 80 * 'default' => 'main_',
webmaster@1 81 * 'users' => 'shared_',
webmaster@1 82 * 'sessions' => 'shared_',
webmaster@1 83 * 'role' => 'shared_',
webmaster@1 84 * 'authmap' => 'shared_',
webmaster@1 85 * );
webmaster@1 86 *
webmaster@1 87 * Database URL format:
webmaster@1 88 * $db_url = 'mysql://username:password@localhost/databasename';
webmaster@1 89 * $db_url = 'mysqli://username:password@localhost/databasename';
webmaster@1 90 * $db_url = 'pgsql://username:password@localhost/databasename';
webmaster@1 91 */
webmaster@1 92 $db_url = 'mysql://username:password@localhost/databasename';
webmaster@1 93 $db_prefix = '';
webmaster@1 94
webmaster@1 95 /**
webmaster@1 96 * Access control for update.php script
webmaster@1 97 *
webmaster@1 98 * If you are updating your Drupal installation using the update.php script
webmaster@1 99 * being not logged in as administrator, you will need to modify the access
webmaster@1 100 * check statement below. Change the FALSE to a TRUE to disable the access
webmaster@1 101 * check. After finishing the upgrade, be sure to open this file again
webmaster@1 102 * and change the TRUE back to a FALSE!
webmaster@1 103 */
webmaster@1 104 $update_free_access = FALSE;
webmaster@1 105
webmaster@1 106 /**
webmaster@1 107 * Base URL (optional).
webmaster@1 108 *
webmaster@1 109 * If you are experiencing issues with different site domains,
webmaster@1 110 * uncomment the Base URL statement below (remove the leading hash sign)
webmaster@1 111 * and fill in the URL to your Drupal installation.
webmaster@1 112 *
webmaster@1 113 * You might also want to force users to use a given domain.
webmaster@1 114 * See the .htaccess file for more information.
webmaster@1 115 *
webmaster@1 116 * Examples:
webmaster@1 117 * $base_url = 'http://www.example.com';
webmaster@1 118 * $base_url = 'http://www.example.com:8888';
webmaster@1 119 * $base_url = 'http://www.example.com/drupal';
webmaster@1 120 * $base_url = 'https://www.example.com:8888/drupal';
webmaster@1 121 *
webmaster@1 122 * It is not allowed to have a trailing slash; Drupal will add it
webmaster@1 123 * for you.
webmaster@1 124 */
webmaster@1 125 # $base_url = 'http://www.example.com'; // NO trailing slash!
webmaster@1 126
webmaster@1 127 /**
webmaster@1 128 * PHP settings:
webmaster@1 129 *
webmaster@1 130 * To see what PHP settings are possible, including whether they can
webmaster@1 131 * be set at runtime (ie., when ini_set() occurs), read the PHP
webmaster@1 132 * documentation at http://www.php.net/manual/en/ini.php#ini.list
webmaster@1 133 * and take a look at the .htaccess file to see which non-runtime
webmaster@1 134 * settings are used there. Settings defined here should not be
webmaster@1 135 * duplicated there so as to avoid conflict issues.
webmaster@1 136 */
webmaster@1 137 ini_set('arg_separator.output', '&amp;');
webmaster@1 138 ini_set('magic_quotes_runtime', 0);
webmaster@1 139 ini_set('magic_quotes_sybase', 0);
webmaster@1 140 ini_set('session.cache_expire', 200000);
webmaster@1 141 ini_set('session.cache_limiter', 'none');
webmaster@1 142 ini_set('session.cookie_lifetime', 2000000);
webmaster@1 143 ini_set('session.gc_maxlifetime', 200000);
webmaster@1 144 ini_set('session.save_handler', 'user');
webmaster@1 145 ini_set('session.use_only_cookies', 1);
webmaster@1 146 ini_set('session.use_trans_sid', 0);
webmaster@1 147 ini_set('url_rewriter.tags', '');
webmaster@1 148
webmaster@1 149 /**
webmaster@1 150 * Drupal automatically generates a unique session cookie name for each site
webmaster@1 151 * based on on its full domain name. If you have multiple domains pointing at
webmaster@1 152 * the same Drupal site, you can either redirect them all to a single domain
webmaster@1 153 * (see comment in .htaccess), or uncomment the line below and specify their
webmaster@1 154 * shared base domain. Doing so assures that users remain logged in as they
webmaster@1 155 * cross between your various domains.
webmaster@1 156 */
webmaster@1 157 # $cookie_domain = 'example.com';
webmaster@1 158
webmaster@1 159 /**
webmaster@1 160 * Variable overrides:
webmaster@1 161 *
webmaster@1 162 * To override specific entries in the 'variable' table for this site,
webmaster@1 163 * set them here. You usually don't need to use this feature. This is
webmaster@1 164 * useful in a configuration file for a vhost or directory, rather than
webmaster@1 165 * the default settings.php. Any configuration setting from the 'variable'
webmaster@1 166 * table can be given a new value. Note that any values you provide in
webmaster@1 167 * these variable overrides will not be modifiable from the Drupal
webmaster@1 168 * administration interface.
webmaster@1 169 *
webmaster@1 170 * Remove the leading hash signs to enable.
webmaster@1 171 */
webmaster@1 172 # $conf = array(
webmaster@1 173 # 'site_name' => 'My Drupal site',
webmaster@1 174 # 'theme_default' => 'minnelli',
webmaster@1 175 # 'anonymous' => 'Visitor',
webmaster@1 176 /**
webmaster@1 177 * A custom theme can be set for the off-line page. This applies when the site
webmaster@1 178 * is explicitly set to off-line mode through the administration page or when
webmaster@1 179 * the database is inactive due to an error. It can be set through the
webmaster@1 180 * 'maintenance_theme' key. The template file should also be copied into the
webmaster@1 181 * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
webmaster@1 182 * Note: This setting does not apply to installation and update pages.
webmaster@1 183 */
webmaster@1 184 # 'maintenance_theme' => 'minnelli',
webmaster@1 185 /**
webmaster@1 186 * reverse_proxy accepts a boolean value.
webmaster@1 187 *
webmaster@1 188 * Enable this setting to determine the correct IP address of the remote
webmaster@1 189 * client by examining information stored in the X-Forwarded-For headers.
webmaster@1 190 * X-Forwarded-For headers are a standard mechanism for identifying client
webmaster@1 191 * systems connecting through a reverse proxy server, such as Squid or
webmaster@1 192 * Pound. Reverse proxy servers are often used to enhance the performance
webmaster@1 193 * of heavily visited sites and may also provide other site caching,
webmaster@1 194 * security or encryption benefits. If this Drupal installation operates
webmaster@1 195 * behind a reverse proxy, this setting should be enabled so that correct
webmaster@1 196 * IP address information is captured in Drupal's session management,
webmaster@1 197 * logging, statistics and access management systems; if you are unsure
webmaster@1 198 * about this setting, do not have a reverse proxy, or Drupal operates in
webmaster@1 199 * a shared hosting environment, this setting should be set to disabled.
webmaster@1 200 */
webmaster@1 201 # 'reverse_proxy' => TRUE,
webmaster@1 202 /**
webmaster@1 203 * reverse_proxy accepts an array of IP addresses.
webmaster@1 204 *
webmaster@1 205 * Each element of this array is the IP address of any of your reverse
webmaster@1 206 * proxies. Filling this array Drupal will trust the information stored
webmaster@1 207 * in the X-Forwarded-For headers only if Remote IP address is one of
webmaster@1 208 * these, that is the request reaches the web server from one of your
webmaster@1 209 * reverse proxies. Otherwise, the client could directly connect to
webmaster@1 210 * your web server spoofing the X-Forwarded-For headers.
webmaster@1 211 */
webmaster@1 212 # 'reverse_proxy_addresses' => array('a.b.c.d', ...),
webmaster@1 213 # );
webmaster@1 214
webmaster@1 215 /**
webmaster@1 216 * String overrides:
webmaster@1 217 *
webmaster@1 218 * To override specific strings on your site with or without enabling locale
webmaster@1 219 * module, add an entry to this list. This functionality allows you to change
webmaster@1 220 * a small number of your site's default English language interface strings.
webmaster@1 221 *
webmaster@1 222 * Remove the leading hash signs to enable.
webmaster@1 223 */
webmaster@1 224 # $conf['locale_custom_strings_en'] = array(
webmaster@1 225 # 'forum' => 'Discussion board',
webmaster@1 226 # '@count min' => '@count minutes',
webmaster@1 227 # );