default.settings.php 19.4 KB
Newer Older
Dries's avatar
 
Dries committed
1
<?php
Dries's avatar
Dries committed
2

Dries's avatar
 
Dries committed
3 4 5
/**
 * @file
 * Drupal site-specific configuration file.
6
 *
7 8 9 10 11 12
 * IMPORTANT NOTE:
 * This file may have been set to read-only by the Drupal installation
 * program. If you make changes to this file, be sure to protect it again
 * after making your modifications. Failure to remove write permissions
 * to this file is a security risk.
 *
Dries's avatar
Dries committed
13
 * The configuration file to be loaded is based upon the rules below.
14 15 16
 *
 * The configuration directory will be discovered by stripping the
 * website's hostname from left to right and pathname from right to
Dries's avatar
Dries committed
17 18
 * left. The first configuration file found will be used and any
 * others will be ignored. If no other configuration file is found
19 20
 * then the default configuration file at 'sites/default' will be used.
 *
21
 * For example, for a fictitious site installed at
Dries's avatar
Dries committed
22 23
 * http://www.drupal.org/mysite/test/, the 'settings.php'
 * is searched in the following directories:
24
 *
25 26 27
 * - sites/www.drupal.org.mysite.test
 * - sites/drupal.org.mysite.test
 * - sites/org.mysite.test
28
 *
29 30 31
 * - sites/www.drupal.org.mysite
 * - sites/drupal.org.mysite
 * - sites/org.mysite
32
 *
33 34 35
 * - sites/www.drupal.org
 * - sites/drupal.org
 * - sites/org
36
 *
37
 * - sites/default
38
 *
39
 * If you are installing on a non-standard port number, prefix the
40
 * hostname with that number. For example,
41
 * http://www.drupal.org:8080/mysite/test/ could be loaded from
42
 * sites/8080.www.drupal.org.mysite.test/.
Dries's avatar
 
Dries committed
43 44
 */

45 46 47
/**
 * Database settings:
 *
48
 * The $databases array specifies the database connection or
49 50 51 52 53 54
 * connections that Drupal may use.  Drupal is able to connect
 * to multiple databases, including multiple types of databases,
 * during the same request.
 *
 * Each database connection is specified as an array of settings,
 * similar to the following:
55
 * @code
56 57 58 59 60 61
 * array(
 *   'driver' => 'mysql',
 *   'database' => 'databasename',
 *   'username' => 'username',
 *   'password' => 'password',
 *   'host' => 'localhost',
62
 *   'port' => 3306,
63
 *   'prefix' => 'myprefix_',
64
 *   'collation' => 'utf8_general_ci',
65
 * );
66
 * @endcode
67
 *
68
 * The "driver" property indicates what Drupal database driver the
69 70 71
 * connection should use.  This is usually the same as the name of the
 * database type, such as mysql or sqlite, but not always.  The other
 * properties will vary depending on the driver.  For SQLite, you must
72 73
 * specify a database file name in a directory that is writable by the
 * webserver.  For most other drivers, you must specify a
74
 * username, password, host, and database name.
75 76
 *
 * Some database engines support transactions.  In order to enable
77
 * transaction support for a given database, set the 'transactions' key
78 79 80 81 82 83 84 85
 * to TRUE.  To disable it, set it to FALSE.  Note that the default value
 * varies by driver.  For MySQL, the default is FALSE since MyISAM tables
 * do not support transactions.
 *
 * For each database, you may optionally specify multiple "target" databases.
 * A target database allows Drupal to try to send certain queries to a
 * different database if it can but fall back to the default connection if not.
 * That is useful for master/slave replication, as Drupal may try to connect
86
 * to a slave server when appropriate and if one is not available will simply
87 88 89
 * fall back to the single master server.
 *
 * The general format for the $databases array is as follows:
90
 * @code
91 92 93
 * $databases['default']['default'] = $info_array;
 * $databases['default']['slave'][] = $info_array;
 * $databases['default']['slave'][] = $info_array;
94
 * $databases['extra']['default'] = $info_array;
95
 * @endcode
96 97 98 99 100 101
 *
 * In the above example, $info_array is an array of settings described above.
 * The first line sets a "default" database that has one master database
 * (the second level default).  The second and third lines create an array
 * of potential slave databases.  Drupal will select one at random for a given
 * request as needed.  The fourth line creates a new database with a name of
102
 * "extra".
103 104
 *
 * For a single database configuration, the following is sufficient:
105
 * @code
106 107 108 109 110 111
 * $databases['default']['default'] = array(
 *   'driver' => 'mysql',
 *   'database' => 'databasename',
 *   'username' => 'username',
 *   'password' => 'password',
 *   'host' => 'localhost',
112
 *   'prefix' => 'main_',
113
 *   'collation' => 'utf8_general_ci',
114
 * );
115
 * @endcode
116
 *
117
 * You can optionally set prefixes for some or all database table names
118
 * by using the 'prefix' setting. If a prefix is specified, the table
119 120 121 122
 * name will be prepended with its value. Be sure to use valid database
 * characters only, usually alphanumeric and underscore. If no prefixes
 * are desired, leave it as an empty string ''.
 *
123
 * To have all database names prefixed, set 'prefix' as a string:
124
 * @code
125
 *   'prefix' => 'main_',
126
 * @endcode
127
 * To provide prefixes for specific tables, set 'prefix' as an array.
128
 * The array's keys are the table names and the values are the prefixes.
129 130
 * The 'default' element is mandatory and holds the prefix for any tables
 * not specified elsewhere in the array. Example:
131
 * @code
132
 *   'prefix' => array(
133
 *     'default'   => 'main_',
134
 *     'users'     => 'shared_',
135 136 137
 *     'sessions'  => 'shared_',
 *     'role'      => 'shared_',
 *     'authmap'   => 'shared_',
138
 *   ),
139
 * @endcode
140
 * You can also use a reference to a schema/database as a prefix. This maybe
141
 * useful if your Drupal installation exists in a schema that is not the default
142
 * or you want to access several databases from the same code base at the same
143 144
 * time.
 * Example:
145
 * @code
146 147 148
 *   'prefix' => array(
 *     'default'   => 'main.',
 *     'users'     => 'shared.',
149 150 151
 *     'sessions'  => 'shared.',
 *     'role'      => 'shared.',
 *     'authmap'   => 'shared.',
152
 *   );
153
 * @endcode
154 155
 * NOTE: MySQL and SQLite's definition of a schema is a database.
 *
156
 * Database configuration format:
157
 * @code
158
 *   $databases['default']['default'] = array(
159 160 161 162 163
 *     'driver' => 'mysql',
 *     'database' => 'databasename',
 *     'username' => 'username',
 *     'password' => 'password',
 *     'host' => 'localhost',
164
 *     'prefix' => '',
165
 *   );
166
 *   $databases['default']['default'] = array(
167 168 169 170 171
 *     'driver' => 'pgsql',
 *     'database' => 'databasename',
 *     'username' => 'username',
 *     'password' => 'password',
 *     'host' => 'localhost',
172
 *     'prefix' => '',
173
 *   );
174
 *   $databases['default']['default'] = array(
175
 *     'driver' => 'sqlite',
176
 *     'database' => '/path/to/databasefilename',
177
 *   );
178
 * @endcode
179
 */
180
$databases = array();
Dries's avatar
 
Dries committed
181

182
/**
183
 * Access control for update.php script.
184
 *
185
 * If you are updating your Drupal installation using the update.php script but
186 187
 * are not logged in using either an account with the "Administer software
 * updates" permission or the site maintenance account (the account that was
188 189 190 191
 * created during installation), you will need to modify the access check
 * statement below. Change the FALSE to a TRUE to disable the access check.
 * After finishing the upgrade, be sure to open this file again and change the
 * TRUE back to a FALSE!
192 193 194
 */
$update_free_access = FALSE;

195 196 197 198 199 200 201 202 203 204 205 206 207 208 209
/**
 * Salt for one-time login links and cancel links, form tokens, etc.
 *
 * This variable will be set to a random value by the installer. All one-time
 * login links will be invalidated if the value is changed.  Note that this
 * variable must have the same value on every web server.  If this variable is
 * empty, a hash of the serialized database credentials will be used as a
 * fallback salt.
 *
 * For enhanced security, you may set this variable to a value using the
 * contents of a file outside your docroot that is never saved together
 * with any backups of your Drupal files and database.
 *
 * Example:
 *   $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
210
 *
211 212 213
 */
$drupal_hash_salt = '';

214
/**
215
 * Base URL (optional).
216
 *
217 218 219 220
 * If Drupal is generating incorrect URLs on your site, which could
 * be in HTML headers (links to CSS and JS files) or visible links on pages
 * (such as in menus), uncomment the Base URL statement below (remove the
 * leading hash sign) and fill in the absolute URL to your Drupal installation.
221 222 223
 *
 * You might also want to force users to use a given domain.
 * See the .htaccess file for more information.
224 225
 *
 * Examples:
226 227 228 229
 *   $base_url = 'http://www.example.com';
 *   $base_url = 'http://www.example.com:8888';
 *   $base_url = 'http://www.example.com/drupal';
 *   $base_url = 'https://www.example.com:8888/drupal';
230 231 232
 *
 * It is not allowed to have a trailing slash; Drupal will add it
 * for you.
233
 */
234
# $base_url = 'http://www.example.com';  // NO trailing slash!
Dries's avatar
 
Dries committed
235

236 237 238
/**
 * PHP settings:
 *
239
 * To see what PHP settings are possible, including whether they can be set at
240
 * runtime (by using ini_set()), read the PHP documentation:
241
 * http://www.php.net/manual/en/ini.list.php
242 243 244
 * See drupal_initialize_variables() in includes/bootstrap.inc for required
 * runtime settings and the .htaccess file for non-runtime settings. Settings
 * defined there should not be duplicated here so as to avoid conflict issues.
245 246 247 248 249 250 251 252 253 254 255 256
 */

/**
 * Some distributions of Linux (most notably Debian) ship their PHP
 * installations with garbage collection (gc) disabled. Since Drupal depends on
 * PHP's garbage collection for clearing sessions, ensure that garbage
 * collection occurs by using the most common settings.
 */
ini_set('session.gc_probability', 1);
ini_set('session.gc_divisor', 100);

/**
257 258 259 260 261 262 263 264 265 266 267
 * Set session lifetime (in seconds), i.e. the time from the user's last visit
 * to the active session may be deleted by the session garbage collector. When
 * a session is deleted, authenticated users are logged out, and the contents
 * of the user's $_SESSION variable is discarded.
 */
ini_set('session.gc_maxlifetime', 200000);

/**
 * Set session cookie lifetime (in seconds), i.e. the time from the session is
 * created to the cookie expires, i.e. when the browser is expected to discard
 * the cookie. The value 0 means "until the browser is closed".
268
 */
269
ini_set('session.cookie_lifetime', 2000000);
Dries's avatar
 
Dries committed
270

271 272 273 274 275 276 277 278 279 280 281
/**
 * If you encounter a situation where users post a large amount of text, and
 * the result is stripped out upon viewing but can still be edited, Drupal's
 * output filter may not have sufficient memory to process it.  If you
 * experience this issue, you may wish to uncomment the following two lines
 * and increase the limits of these variables.  For more information, see
 * http://php.net/manual/en/pcre.configuration.php.
 */
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 200000);

282
/**
283
 * Drupal automatically generates a unique session cookie name for each site
284 285 286 287 288
 * based on its full domain name. If you have multiple domains pointing at the
 * same Drupal site, you can either redirect them all to a single domain (see
 * comment in .htaccess), or uncomment the line below and specify their shared
 * base domain. Doing so assures that users remain logged in as they cross
 * between your various domains.
289 290
 */
# $cookie_domain = 'example.com';
291

292 293 294
/**
 * Variable overrides:
 *
Dries's avatar
Dries committed
295 296 297 298
 * To override specific entries in the 'variable' table for this site,
 * set them here. You usually don't need to use this feature. This is
 * useful in a configuration file for a vhost or directory, rather than
 * the default settings.php. Any configuration setting from the 'variable'
299
 * table can be given a new value. Note that any values you provide in
300
 * these variable overrides will not be modifiable from the Drupal
301
 * administration interface.
302
 *
303 304 305 306
 * The following overrides are examples:
 * - site_name: Defines the site's name.
 * - theme_default: Defines the default theme for this site.
 * - anonymous: Defines the human-readable name of anonymous users.
307
 * Remove the leading hash signs to enable.
308
 */
309
# $conf['site_name'] = 'My Drupal site';
310
# $conf['theme_default'] = 'garland';
311 312
# $conf['anonymous'] = 'Visitor';

313
/**
314
 * A custom theme can be set for the offline page. This applies when the site
315
 * is explicitly set to maintenance mode through the administration page or when
316 317 318 319 320
 * the database is inactive due to an error. It can be set through the
 * 'maintenance_theme' key. The template file should also be copied into the
 * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
 * Note: This setting does not apply to installation and update pages.
 */
321
# $conf['maintenance_theme'] = 'bartik';
322

323 324 325 326 327 328 329 330 331 332 333 334
/**
 * Enable this setting to determine the correct IP address of the remote
 * client by examining information stored in the X-Forwarded-For headers.
 * X-Forwarded-For headers are a standard mechanism for identifying client
 * systems connecting through a reverse proxy server, such as Squid or
 * Pound. Reverse proxy servers are often used to enhance the performance
 * of heavily visited sites and may also provide other site caching,
 * security or encryption benefits. If this Drupal installation operates
 * behind a reverse proxy, this setting should be enabled so that correct
 * IP address information is captured in Drupal's session management,
 * logging, statistics and access management systems; if you are unsure
 * about this setting, do not have a reverse proxy, or Drupal operates in
335
 * a shared hosting environment, this setting should remain commented out.
336
 */
337 338
# $conf['reverse_proxy'] = TRUE;

339 340 341 342 343 344 345 346 347
/**
 * Set this value if your proxy server sends the client IP in a header other
 * than X-Forwarded-For.
 *
 * The "X-Forwarded-For" header is a comma+space separated list of IP addresses,
 * only the last one (the left-most) will be used.
 */
# $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';

348 349 350 351 352 353 354 355 356 357
/**
 * reverse_proxy accepts an array of IP addresses.
 *
 * Each element of this array is the IP address of any of your reverse
 * proxies. Filling this array Drupal will trust the information stored
 * in the X-Forwarded-For headers only if Remote IP address is one of
 * these, that is the request reaches the web server from one of your
 * reverse proxies. Otherwise, the client could directly connect to
 * your web server spoofing the X-Forwarded-For headers.
 */
358
# $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
359

360 361 362 363 364 365 366 367 368 369 370
/**
 * Page caching:
 *
 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
 * views. This tells a HTTP proxy that it may return a page from its local
 * cache without contacting the web server, if the user sends the same Cookie
 * header as the user who originally requested the cached page. Without "Vary:
 * Cookie", authenticated users would also be served the anonymous page from
 * the cache. If the site has mostly anonymous users except a few known
 * editors/administrators, the Vary header can be omitted. This allows for
 * better caching in HTTP proxies (including reverse proxies), i.e. even if
371
 * clients send different cookies, they still get content served from the cache.
372 373 374 375 376 377
 * However, authenticated users should access the site directly (i.e. not use an
 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
 * getting cached pages from the proxy.
 */
# $conf['omit_vary_cookie'] = TRUE;

378 379 380 381 382 383 384 385 386 387 388 389 390 391 392
/**
 * CSS/JS aggregated file gzip compression:
 *
 * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
 * store a gzip compressed (.gz) copy of the aggregated files. If this file is
 * available then rewrite rules in the default .htaccess file will serve these
 * files to browsers that accept gzip encoded content. This allows pages to load
 * faster for these users and has minimal impact on server load. If you are
 * using a webserver other than Apache httpd, or a caching reverse proxy that is
 * configured to cache and compress these files itself you may want to uncomment
 * one or both of the below lines, which will prevent gzip files being stored.
 */
# $conf['css_gzip_compression'] = FALSE;
# $conf['js_gzip_compression'] = FALSE;

393 394 395 396 397 398 399 400 401
/**
 * String overrides:
 *
 * To override specific strings on your site with or without enabling locale
 * module, add an entry to this list. This functionality allows you to change
 * a small number of your site's default English language interface strings.
 *
 * Remove the leading hash signs to enable.
 */
402
# $conf['locale_custom_strings_en'][''] = array(
403 404 405
#   'forum'      => 'Discussion board',
#   '@count min' => '@count minutes',
# );
406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428

/**
 *
 * IP blocking:
 *
 * To bypass database queries for denied IP addresses, use this setting.
 * Drupal queries the {blocked_ips} table by default on every page request
 * for both authenticated and anonymous users. This allows the system to
 * block IP addresses from within the administrative interface and before any
 * modules are loaded. However on high traffic websites you may want to avoid
 * this query, allowing you to bypass database access altogether for anonymous
 * users under certain caching configurations.
 *
 * If using this setting, you will need to add back any IP addresses which
 * you may have blocked via the administrative interface. Each element of this
 * array represents a blocked IP address. Uncommenting the array and leaving it
 * empty will have the effect of disabling IP blocking on your site.
 *
 * Remove the leading hash signs to enable.
 */
# $conf['blocked_ips'] = array(
#   'a.b.c.d',
# );
429

430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465
/**
 * Fast 404 pages:
 *
 * Drupal can generate fully themed 404 pages. However, some of these responses
 * are for images or other resource files that are not displayed to the user.
 * This can waste bandwidth, and also generate server load.
 *
 * The options below return a simple, fast 404 page for URLs matching a
 * specific pattern:
 * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
 *   such as images generated by image styles, or dynamically-resized images.
 *   If you need to add more paths, you can add '|path' to the expression.
 * - 404_fast_paths: A regular expression to match paths that should return a
 *   simple 404 page, rather than the fully themed 404 page. If you don't have
 *   any aliases ending in htm or html you can add '|s?html?' to the expression.
 * - 404_fast_html: The html to return for simple 404 pages.
 *
 * Add leading hash signs if you would like to disable this functionality.
 */
$conf['404_fast_paths_exclude'] = '/\/(?:styles)\//';
$conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
$conf['404_fast_html'] = '<html xmlns="http://www.w3.org/1999/xhtml"><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL "@path" was not found on this server.</p></body></html>';

/**
 * By default, fast 404s are returned as part of the normal page request
 * process, which will properly serve valid pages that happen to match and will
 * also log actual 404s to the Drupal log. Alternatively you can choose to
 * return a 404 now by uncommenting the following line. This will reduce server
 * load, but will cause even valid pages that happen to match the pattern to
 * return 404s, rather than the actual page. It will also prevent the Drupal
 * system log entry. Ensure you understand the effects of this before enabling.
 *
 * To enable this functionality, remove the leading hash sign below.
 */
# drupal_fast_404();

466 467 468 469 470 471 472 473 474 475 476 477 478 479 480
/**
 * Authorized file system operations:
 *
 * The Update manager module included with Drupal provides a mechanism for
 * site administrators to securely install missing updates for the site
 * directly through the web user interface by providing either SSH or FTP
 * credentials. This allows the site to update the new files as the user who
 * owns all the Drupal files, instead of as the user the webserver is running
 * as. However, some sites might wish to disable this functionality, and only
 * update the code directly via SSH or FTP themselves. This setting completely
 * disables all functionality related to these authorized file operations.
 *
 * Remove the leading hash signs to disable.
 */
# $conf['allow_authorize_operations'] = FALSE;