sz8eCW8V

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