w9kzPvK6

1<?php
2
3// @codingStandardsIgnoreFile
4
5/**
6 * @file
7 * Drupal site-specific configuration file.
8 *
9 * IMPORTANT NOTE:
10 * This file may have been set to read-only by the Drupal installation program.
11 * If you make changes to this file, be sure to protect it again after making
12 * your modifications. Failure to remove write permissions to this file is a
13 * security risk.
14 *
15 * In order to use the selection rules below the multisite aliasing file named
16 * sites/sites.php must be present. Its optional settings will be loaded, and
17 * the aliases in the array $sites will override the default directory rules
18 * below. See sites/example.sites.php for more information about aliases.
19 *
20 * The configuration directory will be discovered by stripping the website's
21 * hostname from left to right and pathname from right to left. The first
22 * configuration file found will be used and any others will be ignored. If no
23 * other configuration file is found then the default configuration file at
24 * 'sites/default' will be used.
25 *
26 * For example, for a fictitious site installed at
27 * https://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
28 * for in the following directories:
29 *
30 * - sites/8080.www.drupal.org.mysite.test
31 * - sites/www.drupal.org.mysite.test
32 * - sites/drupal.org.mysite.test
33 * - sites/org.mysite.test
34 *
35 * - sites/8080.www.drupal.org.mysite
36 * - sites/www.drupal.org.mysite
37 * - sites/drupal.org.mysite
38 * - sites/org.mysite
39 *
40 * - sites/8080.www.drupal.org
41 * - sites/www.drupal.org
42 * - sites/drupal.org
43 * - sites/org
44 *
45 * - sites/default
46 *
47 * Note that if you are installing on a non-standard port number, prefix the
48 * hostname with that number. For example,
49 * https://www.drupal.org:8080/mysite/test/ could be loaded from
50 * sites/8080.www.drupal.org.mysite.test/.
51 *
52 * @see example.sites.php
53 * @see \Drupal\Core\DrupalKernel::getSitePath()
54 *
55 * In addition to customizing application settings through variables in
56 * settings.php, you can create a services.yml file in the same directory to
57 * register custom, site-specific service definitions and/or swap out default
58 * implementations with custom ones.
59 */
60
61/**
62 * Database settings:
63 *
64 * The $databases array specifies the database connection or
65 * connections that Drupal may use.  Drupal is able to connect
66 * to multiple databases, including multiple types of databases,
67 * during the same request.
68 *
69 * One example of the simplest connection array is shown below. To use the
70 * sample settings, copy and uncomment the code below between the @code and
71 * @endcode lines and paste it after the $databases declaration. You will need
72 * to replace the database username and password and possibly the host and port
73 * with the appropriate credentials for your database system.
74 *
75 * The next section describes how to customize the $databases array for more
76 * specific needs.
77 *
78 * @code
79 * $databases['default']['default'] = array (
80 *   'database' => 'databasename',
81 *   'username' => 'sqlusername',
82 *   'password' => 'sqlpassword',
83 *   'host' => 'localhost',
84 *   'port' => '3306',
85 *   'driver' => 'mysql',
86 *   'prefix' => '',
87 *   'collation' => 'utf8mb4_general_ci',
88 * );
89 * @endcode
90 */
91$databases = [
92    'default' => [
93        'default' => [
94            'driver' => 'mysql',
95            'username' => '',
96            'password' => '',
97            'host' => '127.0.0.1',
98            'port' => '3306',
99            'prefix' => '',
100            'database' => 'cda2019_d8__default__default',
101            'collation' => 'utf8mb4_general_ci',
102        ]
103    ]
104];
105
106/**
107 * Customizing database settings.
108 *
109 * Many of the values of the $databases array can be customized for your
110 * particular database system. Refer to the sample in the section above as a
111 * starting point.
112 *
113 * The "driver" property indicates what Drupal database driver the
114 * connection should use.  This is usually the same as the name of the
115 * database type, such as mysql or sqlite, but not always.  The other
116 * properties will vary depending on the driver.  For SQLite, you must
117 * specify a database file name in a directory that is writable by the
118 * webserver.  For most other drivers, you must specify a
119 * username, password, host, and database name.
120 *
121 * Transaction support is enabled by default for all drivers that support it,
122 * including MySQL. To explicitly disable it, set the 'transactions' key to
123 * FALSE.
124 * Note that some configurations of MySQL, such as the MyISAM engine, don't
125 * support it and will proceed silently even if enabled. If you experience
126 * transaction related crashes with such configuration, set the 'transactions'
127 * key to FALSE.
128 *
129 * For each database, you may optionally specify multiple "target" databases.
130 * A target database allows Drupal to try to send certain queries to a
131 * different database if it can but fall back to the default connection if not.
132 * That is useful for primary/replica replication, as Drupal may try to connect
133 * to a replica server when appropriate and if one is not available will simply
134 * fall back to the single primary server (The terms primary/replica are
135 * traditionally referred to as master/slave in database server documentation).
136 *
137 * The general format for the $databases array is as follows:
138 * @code
139 * $databases['default']['default'] = $info_array;
140 * $databases['default']['replica'][] = $info_array;
141 * $databases['default']['replica'][] = $info_array;
142 * $databases['extra']['default'] = $info_array;
143 * @endcode
144 *
145 * In the above example, $info_array is an array of settings described above.
146 * The first line sets a "default" database that has one primary database
147 * (the second level default).  The second and third lines create an array
148 * of potential replica databases.  Drupal will select one at random for a given
149 * request as needed.  The fourth line creates a new database with a name of
150 * "extra".
151 *
152 * You can optionally set prefixes for some or all database table names
153 * by using the 'prefix' setting. If a prefix is specified, the table
154 * name will be prepended with its value. Be sure to use valid database
155 * characters only, usually alphanumeric and underscore. If no prefixes
156 * are desired, leave it as an empty string ''.
157 *
158 * To have all database names prefixed, set 'prefix' as a string:
159 * @code
160 *   'prefix' => 'main_',
161 * @endcode
162 *
163 * Per-table prefixes are deprecated as of Drupal 8.2, and will be removed in
164 * Drupal 9.0. After that, only a single prefix for all tables will be
165 * supported.
166 *
167 * To provide prefixes for specific tables, set 'prefix' as an array.
168 * The array's keys are the table names and the values are the prefixes.
169 * The 'default' element is mandatory and holds the prefix for any tables
170 * not specified elsewhere in the array. Example:
171 * @code
172 *   'prefix' => array(
173 *     'default'   => 'main_',
174 *     'users'     => 'shared_',
175 *     'sessions'  => 'shared_',
176 *     'role'      => 'shared_',
177 *     'authmap'   => 'shared_',
178 *   ),
179 * @endcode
180 * You can also use a reference to a schema/database as a prefix. This may be
181 * useful if your Drupal installation exists in a schema that is not the default
182 * or you want to access several databases from the same code base at the same
183 * time.
184 * Example:
185 * @code
186 *   'prefix' => array(
187 *     'default'   => 'main.',
188 *     'users'     => 'shared.',
189 *     'sessions'  => 'shared.',
190 *     'role'      => 'shared.',
191 *     'authmap'   => 'shared.',
192 *   );
193 * @endcode
194 * NOTE: MySQL and SQLite's definition of a schema is a database.
195 *
196 * Advanced users can add or override initial commands to execute when
197 * connecting to the database server, as well as PDO connection settings. For
198 * example, to enable MySQL SELECT queries to exceed the max_join_size system
199 * variable, and to reduce the database connection timeout to 5 seconds:
200 * @code
201 * $databases['default']['default'] = array(
202 *   'init_commands' => array(
203 *     'big_selects' => 'SET SQL_BIG_SELECTS=1',
204 *   ),
205 *   'pdo' => array(
206 *     PDO::ATTR_TIMEOUT => 5,
207 *   ),
208 * );
209 * @endcode
210 *
211 * WARNING: The above defaults are designed for database portability. Changing
212 * them may cause unexpected behavior, including potential data loss. See
213 * https://www.drupal.org/developing/api/database/configuration for more
214 * information on these defaults and the potential issues.
215 *
216 * More details can be found in the constructor methods for each driver:
217 * - \Drupal\Core\Database\Driver\mysql\Connection::__construct()
218 * - \Drupal\Core\Database\Driver\pgsql\Connection::__construct()
219 * - \Drupal\Core\Database\Driver\sqlite\Connection::__construct()
220 *
221 * Sample Database configuration format for PostgreSQL (pgsql):
222 * @code
223 *   $databases['default']['default'] = array(
224 *     'driver' => 'pgsql',
225 *     'database' => 'databasename',
226 *     'username' => 'sqlusername',
227 *     'password' => 'sqlpassword',
228 *     'host' => 'localhost',
229 *     'prefix' => '',
230 *   );
231 * @endcode
232 *
233 * Sample Database configuration format for SQLite (sqlite):
234 * @code
235 *   $databases['default']['default'] = array(
236 *     'driver' => 'sqlite',
237 *     'database' => '/path/to/databasefilename',
238 *   );
239 * @endcode
240 */
241
242/**
243 * Location of the site configuration files.
244 *
245 * The $config_directories array specifies the location of file system
246 * directories used for configuration data. On install, the "sync" directory is
247 * created. This is used for configuration imports. The "active" directory is
248 * not created by default since the default storage for active configuration is
249 * the database rather than the file system. (This can be changed. See "Active
250 * configuration settings" below).
251 *
252 * The default location for the "sync" directory is inside a randomly-named
253 * directory in the public files path. The setting below allows you to override
254 * the "sync" location.
255 *
256 * If you use files for the "active" configuration, you can tell the
257 * Configuration system where this directory is located by adding an entry with
258 * array key CONFIG_ACTIVE_DIRECTORY.
259 *
260 * Example:
261 * @code
262 *   $config_directories = array(
263 *     CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot',
264 *   );
265 * @endcode
266 */
267$config_directories[CONFIG_SYNC_DIRECTORY] = '../{$site_path}/config/sync';
268
269/**
270 * Settings:
271 *
272 * $settings contains environment-specific configuration, such as the files
273 * directory and reverse proxy address, and temporary configuration, such as
274 * security overrides.
275 *
276 * @see \Drupal\Core\Site\Settings::get()
277 */
278
279/**
280 * Salt for one-time login links, cancel links, form tokens, etc.
281 *
282 * This variable will be set to a random value by the installer. All one-time
283 * login links will be invalidated if the value is changed. Note that if your
284 * site is deployed on a cluster of web servers, you must ensure that this
285 * variable has the same value on each server.
286 *
287 * For enhanced security, you may set this variable to the contents of a file
288 * outside your document root; you should also ensure that this file is not
289 * stored with backups of your database.
290 *
291 * Example:
292 * @code
293 *   $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
294 * @endcode
295 */
296$settings['hash_salt'] = 'asd';
297
298/**
299 * Deployment identifier.
300 *
301 * Drupal's dependency injection container will be automatically invalidated and
302 * rebuilt when the Drupal core version changes. When updating contributed or
303 * custom code that changes the container, changing this identifier will also
304 * allow the container to be invalidated as soon as code is deployed.
305 */
306# $settings['deployment_identifier'] = \Drupal::VERSION;
307
308/**
309 * Access control for update.php script.
310 *
311 * If you are updating your Drupal installation using the update.php script but
312 * are not logged in using either an account with the "Administer software
313 * updates" permission or the site maintenance account (the account that was
314 * created during installation), you will need to modify the access check
315 * statement below. Change the FALSE to a TRUE to disable the access check.
316 * After finishing the upgrade, be sure to open this file again and change the
317 * TRUE back to a FALSE!
318 */
319$settings['update_free_access'] = FALSE;
320
321/**
322 * External access proxy settings:
323 *
324 * If your site must access the Internet via a web proxy then you can enter the
325 * proxy settings here. Set the full URL of the proxy, including the port, in
326 * variables:
327 * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP
328 *   requests.
329 * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS
330 *   requests.
331 * You can pass in the user name and password for basic authentication in the
332 * URLs in these settings.
333 *
334 * You can also define an array of host names that can be accessed directly,
335 * bypassing the proxy, in $settings['http_client_config']['proxy']['no'].
336 */
337# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080';
338# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080';
339# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost'];
340
341/**
342 * Reverse Proxy Configuration:
343 *
344 * Reverse proxy servers are often used to enhance the performance
345 * of heavily visited sites and may also provide other site caching,
346 * security, or encryption benefits. In an environment where Drupal
347 * is behind a reverse proxy, the real IP address of the client should
348 * be determined such that the correct client IP address is available
349 * to Drupal's logging, statistics, and access management systems. In
350 * the most simple scenario, the proxy server will add an
351 * X-Forwarded-For header to the request that contains the client IP
352 * address. However, HTTP headers are vulnerable to spoofing, where a
353 * malicious client could bypass restrictions by setting the
354 * X-Forwarded-For header directly. Therefore, Drupal's proxy
355 * configuration requires the IP addresses of all remote proxies to be
356 * specified in $settings['reverse_proxy_addresses'] to work correctly.
357 *
358 * Enable this setting to get Drupal to determine the client IP from
359 * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
360 * If you are unsure about this setting, do not have a reverse proxy,
361 * or Drupal operates in a shared hosting environment, this setting
362 * should remain commented out.
363 *
364 * In order for this setting to be used you must specify every possible
365 * reverse proxy IP address in $settings['reverse_proxy_addresses'].
366 * If a complete list of reverse proxies is not available in your
367 * environment (for example, if you use a CDN) you may set the
368 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
369 * Be aware, however, that it is likely that this would allow IP
370 * address spoofing unless more advanced precautions are taken.
371 */
372# $settings['reverse_proxy'] = TRUE;
373
374/**
375 * Specify every reverse proxy IP address in your environment.
376 * This setting is required if $settings['reverse_proxy'] is TRUE.
377 */
378# $settings['reverse_proxy_addresses'] = ['a.b.c.d', ...];
379
380/**
381 * Set this value if your proxy server sends the client IP in a header
382 * other than X-Forwarded-For.
383 */
384# $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP';
385
386/**
387 * Set this value if your proxy server sends the client protocol in a header
388 * other than X-Forwarded-Proto.
389 */
390# $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO';
391
392/**
393 * Set this value if your proxy server sends the client protocol in a header
394 * other than X-Forwarded-Host.
395 */
396# $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST';
397
398/**
399 * Set this value if your proxy server sends the client protocol in a header
400 * other than X-Forwarded-Port.
401 */
402# $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT';
403
404/**
405 * Set this value if your proxy server sends the client protocol in a header
406 * other than Forwarded.
407 */
408# $settings['reverse_proxy_forwarded_header'] = 'FORWARDED';
409
410/**
411 * Page caching:
412 *
413 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
414 * views. This tells a HTTP proxy that it may return a page from its local
415 * cache without contacting the web server, if the user sends the same Cookie
416 * header as the user who originally requested the cached page. Without "Vary:
417 * Cookie", authenticated users would also be served the anonymous page from
418 * the cache. If the site has mostly anonymous users except a few known
419 * editors/administrators, the Vary header can be omitted. This allows for
420 * better caching in HTTP proxies (including reverse proxies), i.e. even if
421 * clients send different cookies, they still get content served from the cache.
422 * However, authenticated users should access the site directly (i.e. not use an
423 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
424 * getting cached pages from the proxy.
425 */
426# $settings['omit_vary_cookie'] = TRUE;
427
428
429/**
430 * Cache TTL for client error (4xx) responses.
431 *
432 * Items cached per-URL tend to result in a large number of cache items, and
433 * this can be problematic on 404 pages which by their nature are unbounded. A
434 * fixed TTL can be set for these items, defaulting to one hour, so that cache
435 * backends which do not support LRU can purge older entries. To disable caching
436 * of client error responses set the value to 0. Currently applies only to
437 * page_cache module.
438 */
439# $settings['cache_ttl_4xx'] = 3600;
440
441/**
442 * Expiration of cached forms.
443 *
444 * Drupal's Form API stores details of forms in a cache and these entries are
445 * kept for at least 6 hours by default. Expired entries are cleared by cron.
446 *
447 * @see \Drupal\Core\Form\FormCache::setCache()
448 */
449# $settings['form_cache_expiration'] = 21600;
450
451/**
452 * Class Loader.
453 *
454 * If the APC extension is detected, the Symfony APC class loader is used for
455 * performance reasons. Detection can be prevented by setting
456 * class_loader_auto_detect to false, as in the example below.
457 */
458# $settings['class_loader_auto_detect'] = FALSE;
459
460/*
461 * If the APC extension is not detected, either because APC is missing or
462 * because auto-detection has been disabled, auto-loading falls back to
463 * Composer's ClassLoader, which is good for development as it does not break
464 * when code is moved in the file system. You can also decorate the base class
465 * loader with another cached solution than the Symfony APC class loader, as
466 * all production sites should have a cached class loader of some sort enabled.
467 *
468 * To do so, you may decorate and replace the local $class_loader variable. For
469 * example, to use Symfony's APC class loader without automatic detection,
470 * uncomment the code below.
471 */
472/*
473if ($settings['hash_salt']) {
474  $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
475  $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
476  unset($prefix);
477  $class_loader->unregister();
478  $apc_loader->register();
479  $class_loader = $apc_loader;
480}
481*/
482
483/**
484 * Authorized file system operations:
485 *
486 * The Update Manager module included with Drupal provides a mechanism for
487 * site administrators to securely install missing updates for the site
488 * directly through the web user interface. On securely-configured servers,
489 * the Update manager will require the administrator to provide SSH or FTP
490 * credentials before allowing the installation to proceed; this allows the
491 * site to update the new files as the user who owns all the Drupal files,
492 * instead of as the user the webserver is running as. On servers where the
493 * webserver user is itself the owner of the Drupal files, the administrator
494 * will not be prompted for SSH or FTP credentials (note that these server
495 * setups are common on shared hosting, but are inherently insecure).
496 *
497 * Some sites might wish to disable the above functionality, and only update
498 * the code directly via SSH or FTP themselves. This setting completely
499 * disables all functionality related to these authorized file operations.
500 *
501 * @see https://www.drupal.org/node/244924
502 *
503 * Remove the leading hash signs to disable.
504 */
505# $settings['allow_authorize_operations'] = FALSE;
506
507/**
508 * Default mode for directories and files written by Drupal.
509 *
510 * Value should be in PHP Octal Notation, with leading zero.
511 */
512# $settings['file_chmod_directory'] = 0775;
513# $settings['file_chmod_file'] = 0664;
514
515/**
516 * Public file base URL:
517 *
518 * An alternative base URL to be used for serving public files. This must
519 * include any leading directory path.
520 *
521 * A different value from the domain used by Drupal to be used for accessing
522 * public files. This can be used for a simple CDN integration, or to improve
523 * security by serving user-uploaded files from a different domain or subdomain
524 * pointing to the same server. Do not include a trailing slash.
525 */
526# $settings['file_public_base_url'] = 'http://downloads.example.com/files';
527
528/**
529 * Public file path:
530 *
531 * A local file system path where public files will be stored. This directory
532 * must exist and be writable by Drupal. This directory must be relative to
533 * the Drupal installation directory and be accessible over the web.
534 */
535# $settings['file_public_path'] = 'sites/default/files';
536
537/**
538 * Private file path:
539 *
540 * A local file system path where private files will be stored. This directory
541 * must be absolute, outside of the Drupal installation directory and not
542 * accessible over the web.
543 *
544 * Note: Caches need to be cleared when this value is changed to make the
545 * private:// stream wrapper available to the system.
546 *
547 * See https://www.drupal.org/documentation/modules/file for more information
548 * about securing private files.
549 */
550# $settings['file_private_path'] = '';
551
552/**
553 * Session write interval:
554 *
555 * Set the minimum interval between each session write to database.
556 * For performance reasons it defaults to 180.
557 */
558# $settings['session_write_interval'] = 180;
559
560/**
561 * String overrides:
562 *
563 * To override specific strings on your site with or without enabling the Locale
564 * module, add an entry to this list. This functionality allows you to change
565 * a small number of your site's default English language interface strings.
566 *
567 * Remove the leading hash signs to enable.
568 *
569 * The "en" part of the variable name, is dynamic and can be any langcode of
570 * any added language. (eg locale_custom_strings_de for german).
571 */
572# $settings['locale_custom_strings_en'][''] = [
573#   'forum'      => 'Discussion board',
574#   '@count min' => '@count minutes',
575# ];
576
577/**
578 * A custom theme for the offline page:
579 *
580 * This applies when the site is explicitly set to maintenance mode through the
581 * administration page or when the database is inactive due to an error.
582 * The template file should also be copied into the theme. It is located inside
583 * 'core/modules/system/templates/maintenance-page.html.twig'.
584 *
585 * Note: This setting does not apply to installation and update pages.
586 */
587# $settings['maintenance_theme'] = 'bartik';
588
589/**
590 * PHP settings:
591 *
592 * To see what PHP settings are possible, including whether they can be set at
593 * runtime (by using ini_set()), read the PHP documentation:
594 * http://php.net/manual/ini.list.php
595 * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime
596 * settings and the .htaccess file for non-runtime settings.
597 * Settings defined there should not be duplicated here so as to avoid conflict
598 * issues.
599 */
600
601/**
602 * If you encounter a situation where users post a large amount of text, and
603 * the result is stripped out upon viewing but can still be edited, Drupal's
604 * output filter may not have sufficient memory to process it.  If you
605 * experience this issue, you may wish to uncomment the following two lines
606 * and increase the limits of these variables.  For more information, see
607 * http://php.net/manual/pcre.configuration.php.
608 */
609# ini_set('pcre.backtrack_limit', 200000);
610# ini_set('pcre.recursion_limit', 200000);
611
612/**
613 * Active configuration settings.
614 *
615 * By default, the active configuration is stored in the database in the
616 * {config} table. To use a different storage mechanism for the active
617 * configuration, do the following prior to installing:
618 * - Create an "active" directory and declare its path in $config_directories
619 *   as explained under the 'Location of the site configuration files' section
620 *   above in this file. To enhance security, you can declare a path that is
621 *   outside your document root.
622 * - Override the 'bootstrap_config_storage' setting here. It must be set to a
623 *   callable that returns an object that implements
624 *   \Drupal\Core\Config\StorageInterface.
625 * - Override the service definition 'config.storage.active'. Put this
626 *   override in a services.yml file in the same directory as settings.php
627 *   (definitions in this file will override service definition defaults).
628 */
629# $settings['bootstrap_config_storage'] = ['Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage'];
630
631/**
632 * Configuration overrides.
633 *
634 * To globally override specific configuration values for this site,
635 * set them here. You usually don't need to use this feature. This is
636 * useful in a configuration file for a vhost or directory, rather than
637 * the default settings.php.
638 *
639 * Note that any values you provide in these variable overrides will not be
640 * viewable from the Drupal administration interface. The administration
641 * interface displays the values stored in configuration so that you can stage
642 * changes to other environments that don't have the overrides.
643 *
644 * There are particular configuration values that are risky to override. For
645 * example, overriding the list of installed modules in 'core.extension' is not
646 * supported as module install or uninstall has not occurred. Other examples
647 * include field storage configuration, because it has effects on database
648 * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
649 * a way that is not config override aware. Also, note that changing
650 * configuration values in settings.php will not fire any of the configuration
651 * change events.
652 */
653# $config['system.file']['path']['temporary'] = '/tmp';
654# $config['system.site']['name'] = 'My Drupal site';
655# $config['system.theme']['default'] = 'stark';
656# $config['user.settings']['anonymous'] = 'Visitor';
657
658/**
659 * Fast 404 pages:
660 *
661 * Drupal can generate fully themed 404 pages. However, some of these responses
662 * are for images or other resource files that are not displayed to the user.
663 * This can waste bandwidth, and also generate server load.
664 *
665 * The options below return a simple, fast 404 page for URLs matching a
666 * specific pattern:
667 * - $config['system.performance']['fast_404']['exclude_paths']: A regular
668 *   expression to match paths to exclude, such as images generated by image
669 *   styles, or dynamically-resized images. The default pattern provided below
670 *   also excludes the private file system. If you need to add more paths, you
671 *   can add '|path' to the expression.
672 * - $config['system.performance']['fast_404']['paths']: A regular expression to
673 *   match paths that should return a simple 404 page, rather than the fully
674 *   themed 404 page. If you don't have any aliases ending in htm or html you
675 *   can add '|s?html?' to the expression.
676 * - $config['system.performance']['fast_404']['html']: The html to return for
677 *   simple 404 pages.
678 *
679 * Remove the leading hash signs if you would like to alter this functionality.
680 */
681# $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
682# $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
683# $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>';
684
685/**
686 * Load services definition file.
687 */
688$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
689
690/**
691 * Override the default service container class.
692 *
693 * This is useful for example to trace the service container for performance
694 * tracking purposes, for testing a service container with an error condition or
695 * to test a service container that throws an exception.
696 */
697# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
698
699/**
700 * Override the default yaml parser class.
701 *
702 * Provide a fully qualified class name here if you would like to provide an
703 * alternate implementation YAML parser. The class must implement the
704 * \Drupal\Component\Serialization\SerializationInterface interface.
705 */
706# $settings['yaml_parser_class'] = NULL;
707
708/**
709 * Trusted host configuration.
710 *
711 * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
712 * header spoofing.
713 *
714 * To enable the trusted host mechanism, you enable your allowable hosts
715 * in $settings['trusted_host_patterns']. This should be an array of regular
716 * expression patterns, without delimiters, representing the hosts you would
717 * like to allow.
718 *
719 * For example:
720 * @code
721 * $settings['trusted_host_patterns'] = array(
722 *   '^www\.example\.com$',
723 * );
724 * @endcode
725 * will allow the site to only run from www.example.com.
726 *
727 * If you are running multisite, or if you are running your site from
728 * different domain names (eg, you don't redirect http://www.example.com to
729 * http://example.com), you should specify all of the host patterns that are
730 * allowed by your site.
731 *
732 * For example:
733 * @code
734 * $settings['trusted_host_patterns'] = array(
735 *   '^example\.com$',
736 *   '^.+\.example\.com$',
737 *   '^example\.org$',
738 *   '^.+\.example\.org$',
739 * );
740 * @endcode
741 * will allow the site to run off of all variants of example.com and
742 * example.org, with all subdomains included.
743 */
744
745/**
746 * The default list of directories that will be ignored by Drupal's file API.
747 *
748 * By default ignore node_modules and bower_components folders to avoid issues
749 * with common frontend tools and recursive scanning of directories looking for
750 * extensions.
751 *
752 * @see file_scan_directory()
753 * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory()
754 */
755$settings['file_scan_ignore_directories'] = [
756  'node_modules',
757  'bower_components',
758];
759
760/**
761 * The default number of entities to update in a batch process.
762 *
763 * This is used by update and post-update functions that need to go through and
764 * change all the entities on a site, so it is useful to increase this number
765 * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a
766 * larger number of entities to be processed in a single batch run.
767 */
768$settings['entity_update_batch_size'] = 50;
769
770/**
771 * Load local development override configuration, if available.
772 *
773 * Use settings.local.php to override variables on secondary (staging,
774 * development, etc) installations of this site. Typically used to disable
775 * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
776 * other things that should not happen on development and testing sites.
777 *
778 * Keep this code block at the end of this file to take full effect.
779 */
780
781if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
782    include $app_root . '/' . $site_path . '/settings.local.php';
783}