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

3 4 5
/**
 * @file
 * Drupal site-specific configuration file.
6
 *
7
 * IMPORTANT NOTE:
8 9 10 11 12
 * 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.
 *
13 14 15 16
 * In order to use the selection rules below the multisite aliasing file named
 * sites/sites.php must be present. Its optional settings will be loaded, and
 * the aliases in the array $sites will override the default directory rules
 * below. See sites/example.sites.php for more information about aliases.
17 18 19 20 21 22
 *
 * The configuration directory will be discovered by stripping the website's
 * hostname from left to right and pathname from right to left. The first
 * configuration file found will be used and any others will be ignored. If no
 * other configuration file is found then the default configuration file at
 * 'sites/default' will be used.
23
 *
24
 * For example, for a fictitious site installed at
25
 * https://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
26
 * for in the following directories:
27
 *
28
 * - sites/8080.www.drupal.org.mysite.test
29 30 31
 * - sites/www.drupal.org.mysite.test
 * - sites/drupal.org.mysite.test
 * - sites/org.mysite.test
32
 *
33
 * - sites/8080.www.drupal.org.mysite
34 35 36
 * - sites/www.drupal.org.mysite
 * - sites/drupal.org.mysite
 * - sites/org.mysite
37
 *
38
 * - sites/8080.www.drupal.org
39 40 41
 * - sites/www.drupal.org
 * - sites/drupal.org
 * - sites/org
42
 *
43
 * - sites/default
44
 *
45
 * Note that if you are installing on a non-standard port number, prefix the
46
 * hostname with that number. For example,
47
 * https://www.drupal.org:8080/mysite/test/ could be loaded from
48
 * sites/8080.www.drupal.org.mysite.test/.
49 50
 *
 * @see example.sites.php
51
 * @see \Drupal\Core\DrupalKernel::getSitePath()
52 53 54 55 56
 *
 * In addition to customizing application settings through variables in
 * settings.php, you can create a services.yml file in the same directory to
 * register custom, site-specific service definitions and/or swap out default
 * implementations with custom ones.
57 58
 */

59 60 61
/**
 * Database settings:
 *
62
 * The $databases array specifies the database connection or
63 64 65 66 67 68
 * 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:
69
 * @code
70 71 72 73 74 75
 * array(
 *   'driver' => 'mysql',
 *   'database' => 'databasename',
 *   'username' => 'username',
 *   'password' => 'password',
 *   'host' => 'localhost',
76
 *   'port' => 3306,
77
 *   'prefix' => 'myprefix_',
78
 *   'collation' => 'utf8mb4_general_ci',
79
 * );
80
 * @endcode
81
 *
82
 * The "driver" property indicates what Drupal database driver the
83 84 85
 * 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
86 87
 * specify a database file name in a directory that is writable by the
 * webserver.  For most other drivers, you must specify a
88
 * username, password, host, and database name.
89
 *
90 91 92 93 94 95 96
 * Transaction support is enabled by default for all drivers that support it,
 * including MySQL. To explicitly disable it, set the 'transactions' key to
 * FALSE.
 * Note that some configurations of MySQL, such as the MyISAM engine, don't
 * support it and will proceed silently even if enabled. If you experience
 * transaction related crashes with such configuration, set the 'transactions'
 * key to FALSE.
97 98 99 100
 *
 * 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.
101 102 103 104
 * That is useful for primary/replica replication, as Drupal may try to connect
 * to a replica server when appropriate and if one is not available will simply
 * fall back to the single primary server (The terms primary/replica are
 * traditionally referred to as master/slave in database server documentation).
105 106
 *
 * The general format for the $databases array is as follows:
107
 * @code
108
 * $databases['default']['default'] = $info_array;
109 110
 * $databases['default']['replica'][] = $info_array;
 * $databases['default']['replica'][] = $info_array;
111
 * $databases['extra']['default'] = $info_array;
112
 * @endcode
113 114
 *
 * In the above example, $info_array is an array of settings described above.
115
 * The first line sets a "default" database that has one primary database
116
 * (the second level default).  The second and third lines create an array
117
 * of potential replica databases.  Drupal will select one at random for a given
118
 * request as needed.  The fourth line creates a new database with a name of
119
 * "extra".
120 121
 *
 * For a single database configuration, the following is sufficient:
122
 * @code
123 124 125 126 127 128
 * $databases['default']['default'] = array(
 *   'driver' => 'mysql',
 *   'database' => 'databasename',
 *   'username' => 'username',
 *   'password' => 'password',
 *   'host' => 'localhost',
129
 *   'prefix' => 'main_',
130
 *   'collation' => 'utf8mb4_general_ci',
131
 * );
132
 * @endcode
133
 *
134
 * You can optionally set prefixes for some or all database table names
135
 * by using the 'prefix' setting. If a prefix is specified, the table
136 137 138 139
 * 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 ''.
 *
140
 * To have all database names prefixed, set 'prefix' as a string:
141
 * @code
142
 *   'prefix' => 'main_',
143
 * @endcode
144
 * To provide prefixes for specific tables, set 'prefix' as an array.
145
 * The array's keys are the table names and the values are the prefixes.
146 147
 * The 'default' element is mandatory and holds the prefix for any tables
 * not specified elsewhere in the array. Example:
148
 * @code
149
 *   'prefix' => array(
150
 *     'default'   => 'main_',
151
 *     'users'     => 'shared_',
152 153 154
 *     'sessions'  => 'shared_',
 *     'role'      => 'shared_',
 *     'authmap'   => 'shared_',
155
 *   ),
156
 * @endcode
157
 * You can also use a reference to a schema/database as a prefix. This may be
158
 * useful if your Drupal installation exists in a schema that is not the default
159
 * or you want to access several databases from the same code base at the same
160 161
 * time.
 * Example:
162
 * @code
163 164 165
 *   'prefix' => array(
 *     'default'   => 'main.',
 *     'users'     => 'shared.',
166 167 168
 *     'sessions'  => 'shared.',
 *     'role'      => 'shared.',
 *     'authmap'   => 'shared.',
169
 *   );
170
 * @endcode
171 172
 * NOTE: MySQL and SQLite's definition of a schema is a database.
 *
173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195
 * Advanced users can add or override initial commands to execute when
 * connecting to the database server, as well as PDO connection settings. For
 * example, to enable MySQL SELECT queries to exceed the max_join_size system
 * variable, and to reduce the database connection timeout to 5 seconds:
 *
 * @code
 * $databases['default']['default'] = array(
 *   'init_commands' => array(
 *     'big_selects' => 'SET SQL_BIG_SELECTS=1',
 *   ),
 *   'pdo' => array(
 *     PDO::ATTR_TIMEOUT => 5,
 *   ),
 * );
 * @endcode
 *
 * WARNING: These defaults are designed for database portability. Changing them
 * may cause unexpected behavior, including potential data loss.
 *
 * @see DatabaseConnection_mysql::__construct
 * @see DatabaseConnection_pgsql::__construct
 * @see DatabaseConnection_sqlite::__construct
 *
196
 * Database configuration format:
197
 * @code
198
 *   $databases['default']['default'] = array(
199 200 201 202 203
 *     'driver' => 'mysql',
 *     'database' => 'databasename',
 *     'username' => 'username',
 *     'password' => 'password',
 *     'host' => 'localhost',
204
 *     'prefix' => '',
205
 *   );
206
 *   $databases['default']['default'] = array(
207 208 209 210 211
 *     'driver' => 'pgsql',
 *     'database' => 'databasename',
 *     'username' => 'username',
 *     'password' => 'password',
 *     'host' => 'localhost',
212
 *     'prefix' => '',
213
 *   );
214
 *   $databases['default']['default'] = array(
215
 *     'driver' => 'sqlite',
216
 *     'database' => '/path/to/databasefilename',
217
 *   );
218
 * @endcode
219
 */
220
$databases = array();
221

222 223 224
/**
 * Location of the site configuration files.
 *
225 226 227 228 229 230 231 232 233 234 235 236
 * The $config_directories array specifies the location of file system
 * directories used for configuration data. On install, "active" and "staging"
 * directories are created for configuration. The staging directory is used for
 * configuration imports; the active directory is not used by default, since the
 * default storage for active configuration is the database rather than the file
 * system (this can be changed; see "Active configuration settings" below).
 *
 * The default location for the active and staging directories is inside a
 * randomly-named directory in the public files path; this setting allows you to
 * override these locations. If you use files for the active configuration, you
 * can enhance security by putting the active configuration outside your
 * document root.
237 238
 *
 * Example:
239 240
 * @code
 *   $config_directories = array(
241
 *     CONFIG_STAGING_DIRECTORY => '/another/directory/outside/webroot',
242 243
 *   );
 * @endcode
244
 */
245
$config_directories = array();
246

247 248 249
/**
 * Settings:
 *
250 251
 * $settings contains environment-specific configuration, such as the files
 * directory and reverse proxy address, and temporary configuration, such as
252
 * security overrides.
253
 *
254
 * @see \Drupal\Core\Site\Settings::get()
255 256
 */

257 258 259 260 261 262 263 264 265 266 267 268
/**
 * The active installation profile.
 *
 * Changing this after installation is not recommended as it changes which
 * directories are scanned during extension discovery. If this is set prior to
 * installation this value will be rewritten according to the profile selected
 * by the user.
 *
 * @see install_select_profile()
 */
# $settings['install_profile'] = '';

269 270 271 272 273 274 275 276
/**
 * Salt for one-time login links, 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 if your
 * site is deployed on a cluster of web servers, you must ensure that this
 * variable has the same value on each server.
 *
277 278 279
 * For enhanced security, you may set this variable to the contents of a file
 * outside your document root; you should also ensure that this file is not
 * stored with backups of your database.
280 281 282 283 284 285 286 287
 *
 * Example:
 * @code
 *   $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
 * @endcode
 */
$settings['hash_salt'] = '';

288 289 290 291 292 293 294 295 296 297
/**
 * Deployment identifier.
 *
 * Drupal's dependency injection container will be automatically invalidated and
 * rebuilt when the Drupal core version changes. When updating contributed or
 * custom code that changes the container, changing this identifier will also
 * allow the container to be invalidated as soon as code is deployed.
 */
# $settings['deployment_identifier'] = \Drupal::VERSION;

298 299 300 301 302 303 304 305 306 307 308 309
/**
 * Access control for update.php script.
 *
 * If you are updating your Drupal installation using the update.php script but
 * are not logged in using either an account with the "Administer software
 * updates" permission or the site maintenance account (the account that was
 * 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!
 */
$settings['update_free_access'] = FALSE;
310

311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394
/**
 * External access proxy settings:
 *
 * If your site must access the Internet via a web proxy then you can enter
 * the proxy settings here. Currently only basic authentication is supported
 * by using the username and password variables. The proxy_user_agent variable
 * can be set to NULL for proxies that require no User-Agent header or to a
 * non-empty string for proxies that limit requests to a specific agent. The
 * proxy_exceptions variable is an array of host names to be accessed directly,
 * not via proxy.
 */
# $settings['proxy_server'] = '';
# $settings['proxy_port'] = 8080;
# $settings['proxy_username'] = '';
# $settings['proxy_password'] = '';
# $settings['proxy_user_agent'] = '';
# $settings['proxy_exceptions'] = array('127.0.0.1', 'localhost');

/**
 * Reverse Proxy Configuration:
 *
 * 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. In an environment where Drupal
 * is behind a reverse proxy, the real IP address of the client should
 * be determined such that the correct client IP address is available
 * to Drupal's logging, statistics, and access management systems. In
 * the most simple scenario, the proxy server will add an
 * X-Forwarded-For header to the request that contains the client IP
 * address. However, HTTP headers are vulnerable to spoofing, where a
 * malicious client could bypass restrictions by setting the
 * X-Forwarded-For header directly. Therefore, Drupal's proxy
 * configuration requires the IP addresses of all remote proxies to be
 * specified in $settings['reverse_proxy_addresses'] to work correctly.
 *
 * Enable this setting to get Drupal to determine the client IP from
 * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
 * If you are unsure about this setting, do not have a reverse proxy,
 * or Drupal operates in a shared hosting environment, this setting
 * should remain commented out.
 *
 * In order for this setting to be used you must specify every possible
 * reverse proxy IP address in $settings['reverse_proxy_addresses'].
 * If a complete list of reverse proxies is not available in your
 * environment (for example, if you use a CDN) you may set the
 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
 * Be aware, however, that it is likely that this would allow IP
 * address spoofing unless more advanced precautions are taken.
 */
# $settings['reverse_proxy'] = TRUE;

/**
 * Specify every reverse proxy IP address in your environment.
 * This setting is required if $settings['reverse_proxy'] is TRUE.
 */
# $settings['reverse_proxy_addresses'] = array('a.b.c.d', ...);

/**
 * Set this value if your proxy server sends the client IP in a header
 * other than X-Forwarded-For.
 */
# $settings['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';

/**
 * 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
 * clients send different cookies, they still get content served from the cache.
 * 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.
 */
# $settings['omit_vary_cookie'] = TRUE;

/**
 * Class Loader.
 *
395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411
 * If the APC extension is detected, the Symfony APC class loader is used for
 * performance reasons. Detection can be prevented by setting
 * class_loader_auto_detect to false, as in the example below.
 */
# $settings['class_loader_auto_detect'] = FALSE;

/*
 * If the APC extension is not detected, either because APC is missing or
 * because auto-detection has been disabled, auto-loading falls back to
 * Composer's ClassLoader, which is good for development as it does not break
 * when code is moved in the file system. You can also decorate the base class
 * loader with another cached solution than the Symfony APC class loader, as
 * all production sites should have a cached class loader of some sort enabled.
 *
 * To do so, you may decorate and replace the local $class_loader variable. For
 * example, to use Symfony's APC class loader without automatic detection,
 * uncomment the code below.
412
 */
413 414
/*
if ($settings['hash_salt']) {
415 416 417
  $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
  $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
  unset($prefix);
418 419 420 421 422
  $class_loader->unregister();
  $apc_loader->register();
  $class_loader = $apc_loader;
}
*/
423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441

/**
 * 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. On securely-configured servers,
 * the Update manager will require the administrator to provide SSH or FTP
 * credentials before allowing the installation to proceed; 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. On servers where the
 * webserver user is itself the owner of the Drupal files, the administrator
 * will not be prompted for SSH or FTP credentials (note that these server
 * setups are common on shared hosting, but are inherently insecure).
 *
 * Some sites might wish to disable the above functionality, and only update
 * the code directly via SSH or FTP themselves. This setting completely
 * disables all functionality related to these authorized file operations.
 *
442
 * @see https://www.drupal.org/node/244924
443 444 445 446 447
 *
 * Remove the leading hash signs to disable.
 */
# $settings['allow_authorize_operations'] = FALSE;

448 449 450 451 452 453 454 455
/**
 * Default mode for for directories and files written by Drupal.
 *
 * Value should be in PHP Octal Notation, with leading zero.
 */
# $settings['file_chmod_directory'] = 0775;
# $settings['file_chmod_file'] = 0664;

456 457 458 459 460 461 462 463 464 465 466 467 468
/**
 * Public file base URL:
 *
 * An alternative base URL to be used for serving public files. This must
 * include any leading directory path.
 *
 * A different value from the domain used by Drupal to be used for accessing
 * public files. This can be used for a simple CDN integration, or to improve
 * security by serving user-uploaded files from a different domain or subdomain
 * pointing to the same server. Do not include a trailing slash.
 */
# $settings['file_public_base_url'] = 'http://downloads.example.com/files';

469 470 471 472 473 474 475 476 477
/**
 * Public file path:
 *
 * A local file system path where public files will be stored. This directory
 * must exist and be writable by Drupal. This directory must be relative to
 * the Drupal installation directory and be accessible over the web.
 */
# $settings['file_public_path'] = 'sites/default/files';

478 479 480 481
/**
 * Private file path:
 *
 * A local file system path where private files will be stored. This directory
482
 * must be absolute, outside of the Drupal installation directory and not
483 484
 * accessible over the web.
 *
485 486 487
 * Note: Caches need to be cleared when this value is changed to make the
 * private:// stream wrapper available to the system.
 *
488 489
 * See https://www.drupal.org/documentation/modules/file for more information
 * about securing private files.
490 491 492
 */
# $settings['file_private_path'] = '';

493 494 495 496 497 498 499 500
/**
 * Session write interval:
 *
 * Set the minimum interval between each session write to database.
 * For performance reasons it defaults to 180.
 */
# $settings['session_write_interval'] = 180;

501 502 503 504 505 506 507 508 509 510
/**
 * String overrides:
 *
 * To override specific strings on your site with or without enabling the 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.
 *
 * The "en" part of the variable name, is dynamic and can be any langcode of
511
 * any added language. (eg locale_custom_strings_de for german).
512 513 514 515 516 517
 */
# $settings['locale_custom_strings_en'][''] = array(
#   'forum'      => 'Discussion board',
#   '@count min' => '@count minutes',
# );

518 519 520 521 522 523
/**
 * A custom theme for the offline page:
 *
 * This applies when the site is explicitly set to maintenance mode through the
 * administration page or when the database is inactive due to an error.
 * The template file should also be copied into the theme. It is located inside
524 525
 * 'core/modules/system/templates/maintenance-page.html.twig'.
 *
526 527 528 529
 * Note: This setting does not apply to installation and update pages.
 */
# $settings['maintenance_theme'] = 'bartik';

530 531 532
/**
 * PHP settings:
 *
533
 * To see what PHP settings are possible, including whether they can be set at
534
 * runtime (by using ini_set()), read the PHP documentation:
535
 * http://php.net/manual/ini.list.php
536 537
 * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime
 * settings and the .htaccess file for non-runtime settings.
538 539
 * Settings defined there should not be duplicated here so as to avoid conflict
 * issues.
540 541
 */

542 543 544 545 546 547
/**
 * 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
548
 * http://php.net/manual/pcre.configuration.php.
549 550 551 552
 */
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 200000);

553 554 555 556
/**
 * Active configuration settings.
 *
 * By default, the active configuration is stored in the database in the
557 558 559 560 561 562 563 564
 * {config} table. To use a different storage mechanism for the active
 * configuration, do the following prior to installing:
 * - Override the 'bootstrap_config_storage' setting here. It must be set to a
 *   callable that returns an object that implements
 *   \Drupal\Core\Config\StorageInterface.
 * - Override the service definition 'config.storage.active'. Put this
 *   override in a services.yml file in the same directory as settings.php
 *   (definitions in this file will override service definition defaults).
565
 */
566
# $settings['bootstrap_config_storage'] = array('Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage');
567

568
/**
569
 * Configuration overrides.
570
 *
571
 * To globally override specific configuration values for this site,
Dries's avatar
Dries committed
572 573
 * 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
574 575 576
 * the default settings.php.
 *
 * Note that any values you provide in these variable overrides will not be
577 578 579 580 581 582 583 584 585 586 587 588
 * viewable from the Drupal administration interface. The administration
 * interface displays the values stored in configuration so that you can stage
 * changes to other environments that don't have the overrides.
 *
 * There are particular configuration values that are risky to override. For
 * example, overriding the list of installed modules in 'core.extension' is not
 * supported as module install or uninstall has not occurred. Other examples
 * include field storage configuration, because it has effects on database
 * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
 * a way that is not config override aware. Also, note that changing
 * configuration values in settings.php will not fire any of the configuration
 * change events.
589
 */
590 591 592
# $config['system.site']['name'] = 'My Drupal site';
# $config['system.theme']['default'] = 'stark';
# $config['user.settings']['anonymous'] = 'Visitor';
593

594 595 596 597 598 599 600 601 602
/**
 * 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:
603
 * - $config['system.performance']['fast_404']['exclude_paths']: A regular
604
 *   expression to match paths to exclude, such as images generated by image
605 606
 *   styles, or dynamically-resized images. The default pattern provided below
 *   also excludes the private file system. If you need to add more paths, you
607
 *   can add '|path' to the expression.
608
 * - $config['system.performance']['fast_404']['paths']: A regular expression to
609 610 611
 *   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.
612
 * - $config['system.performance']['fast_404']['html']: The html to return for
613
 *   simple 404 pages.
614
 *
615
 * Remove the leading hash signs if you would like to alter this functionality.
616
 */
617
# $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
618 619
# $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
# $config['system.performance']['fast_404']['html'] = '<!DOCTYPE html><html><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>';
620

621 622 623 624 625
/**
 * Load services definition file.
 */
$settings['container_yamls'][] = __DIR__ . '/services.yml';

626 627 628 629 630 631 632 633 634
/**
 * Override the default service container class.
 *
 * This is useful for example to trace the service container for performance
 * tracking purposes, for testing a service container with an error condition or
 * to test a service container that throws an exception.
 */
# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';

635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663
/**
 * Trusted host configuration.
 *
 * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
 * header spoofing.
 *
 * To enable the trusted host mechanism, you enable your allowable hosts
 * in $settings['trusted_host_patterns']. This should be an array of regular
 * expression patterns, without delimiters, representing the hosts you would
 * like to allow.
 *
 * For example:
 * @code
 * $settings['trusted_host_patterns'] = array(
 *   '^www\.example\.com$',
 * );
 * @endcode
 * will allow the site to only run from www.example.com.
 *
 * If you are running multisite, or if you are running your site from
 * different domain names (eg, you don't redirect http://www.example.com to
 * http://example.com), you should specify all of the host patterns that are
 * allowed by your site.
 *
 * For example:
 * @code
 * $settings['trusted_host_patterns'] = array(
 *   '^example\.com$',
 *   '^.+\.example\.com$',
664 665
 *   '^example\.org$',
 *   '^.+\.example\.org$',
666 667 668 669 670
 * );
 * @endcode
 * will allow the site to run off of all variants of example.com and
 * example.org, with all subdomains included.
 */
671 672 673 674 675 676 677 678 679 680 681 682 683 684

/**
 * Load local development override configuration, if available.
 *
 * Use settings.local.php to override variables on secondary (staging,
 * development, etc) installations of this site. Typically used to disable
 * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
 * other things that should not happen on development and testing sites.
 *
 * Keep this code block at the end of this file to take full effect.
 */
# if (file_exists(__DIR__ . '/settings.local.php')) {
#   include __DIR__ . '/settings.local.php';
# }