rpeazck3

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