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