cXxUNqQm

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