UUHJU6Kj

1<?php
2
3// @codingStandardsIgnoreFile
4
5/**
6 * @file
7 * Drupal site-specific configuration file.
8 *
9 * IMPORTANT NOTE:
10 * This file may have been set to read-only by the Drupal installation program.
11 * If you make changes to this file, be sure to protect it again after making
12 * your modifications. Failure to remove write permissions to this file is a
13 * security risk.
14 *
15 * In order to use the selection rules below the multisite aliasing file named
16 * sites/sites.php must be present. Its optional settings will be loaded, and
17 * the aliases in the array $sites will override the default directory rules
18 * below. See sites/example.sites.php for more information about aliases.
19 *
20 * The configuration directory will be discovered by stripping the website's
21 * hostname from left to right and pathname from right to left. The first
22 * configuration file found will be used and any others will be ignored. If no
23 * other configuration file is found then the default configuration file at
24 * 'sites/default' will be used.
25 *
26 * For example, for a fictitious site installed at
27 * https://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
28 * for in the following directories:
29 *
30 * - sites/8080.www.drupal.org.mysite.test
31 * - sites/www.drupal.org.mysite.test
32 * - sites/drupal.org.mysite.test
33 * - sites/org.mysite.test
34 *
35 * - sites/8080.www.drupal.org.mysite
36 * - sites/www.drupal.org.mysite
37 * - sites/drupal.org.mysite
38 * - sites/org.mysite
39 *
40 * - sites/8080.www.drupal.org
41 * - sites/www.drupal.org
42 * - sites/drupal.org
43 * - sites/org
44 *
45 * - sites/default
46 *
47 * Note that if you are installing on a non-standard port number, prefix the
48 * hostname with that number. For example,
49 * https://www.drupal.org:8080/mysite/test/ could be loaded from
50 * sites/8080.www.drupal.org.mysite.test/.
51 *
52 * @see example.sites.php
53 * @see \Drupal\Core\DrupalKernel::getSitePath()
54 *
55 * In addition to customizing application settings through variables in
56 * settings.php, you can create a services.yml file in the same directory to
57 * register custom, site-specific service definitions and/or swap out default
58 * implementations with custom ones.
59 */
60
61/**
62 * Database settings:
63 *
64 * The $databases array specifies the database connection or
65 * connections that Drupal may use.  Drupal is able to connect
66 * to multiple databases, including multiple types of databases,
67 * during the same request.
68 *
69 * One example of the simplest connection array is shown below. To use the
70 * sample settings, copy and uncomment the code below between the @code and
71 * @endcode lines and paste it after the $databases declaration. You will need
72 * to replace the database username and password and possibly the host and port
73 * with the appropriate credentials for your database system.
74 *
75 * The next section describes how to customize the $databases array for more
76 * specific needs.
77 *
78 * @code
79 * $databases['default']['default'] = array (
80 *   'database' => 'databasename',
81 *   'username' => 'sqlusername',
82 *   'password' => 'sqlpassword',
83 *   'host' => 'localhost',
84 *   'port' => '3306',
85 *   'driver' => 'mysql',
86 *   'prefix' => '',
87 *   'collation' => 'utf8mb4_general_ci',
88 * );
89 * @endcode
90 */
91$databases = [];
92
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' => array(
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' => array(
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'] = array(
189 *   'init_commands' => array(
190 *     'big_selects' => 'SET SQL_BIG_SELECTS=1',
191 *   ),
192 *   'pdo' => array(
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'] = array(
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'] = array(
223 *     'driver' => 'sqlite',
224 *     'database' => '/path/to/databasefilename',
225 *   );
226 * @endcode
227 */
228
229/**
230 * Location of the site configuration files.
231 *
232 * The $config_directories array specifies the location of file system
233 * directories used for configuration data. On install, the "sync" directory is
234 * created. This is used for configuration imports. The "active" directory is
235 * not created by default since the default storage for active configuration is
236 * the database rather than the file system. (This can be changed. See "Active
237 * configuration settings" below).
238 *
239 * The default location for the "sync" directory is inside a randomly-named
240 * directory in the public files path. The setting below allows you to override
241 * the "sync" location.
242 *
243 * If you use files for the "active" configuration, you can tell the
244 * Configuration system where this directory is located by adding an entry with
245 * array key CONFIG_ACTIVE_DIRECTORY.
246 *
247 * Example:
248 * @code
249 *   $config_directories = array(
250 *     CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot',
251 *   );
252 * @endcode
253 */
254$config_directories = [];
255
256/**
257 * Settings:
258 *
259 * $settings contains environment-specific configuration, such as the files
260 * directory and reverse proxy address, and temporary configuration, such as
261 * security overrides.
262 *
263 * @see \Drupal\Core\Site\Settings::get()
264 */
265
266/**
267 * Salt for one-time login links, cancel links, form tokens, etc.
268 *
269 * This variable will be set to a random value by the installer. All one-time
270 * login links will be invalidated if the value is changed. Note that if your
271 * site is deployed on a cluster of web servers, you must ensure that this
272 * variable has the same value on each server.
273 *
274 * For enhanced security, you may set this variable to the contents of a file
275 * outside your document root; you should also ensure that this file is not
276 * stored with backups of your database.
277 *
278 * Example:
279 * @code
280 *   $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
281 * @endcode
282 */
283$settings['hash_salt'] = '-8NUW_R2cUow3RPZhmhdFPGsG5nQPRYkSPh7mMoqX4_QD907AF9Te0s4j5Zan4OnJ7wQ8PGZNQ';
284/**
285 * Deployment identifier.
286 *
287 * Drupal's dependency injection container will be automatically invalidated and
288 * rebuilt when the Drupal core version changes. When updating contributed or
289 * custom code that changes the container, changing this identifier will also
290 * allow the container to be invalidated as soon as code is deployed.
291 */
292# $settings['deployment_identifier'] = \Drupal::VERSION;
293
294/**
295 * Access control for update.php script.
296 *
297 * If you are updating your Drupal installation using the update.php script but
298 * are not logged in using either an account with the "Administer software
299 * updates" permission or the site maintenance account (the account that was
300 * created during installation), you will need to modify the access check
301 * statement below. Change the FALSE to a TRUE to disable the access check.
302 * After finishing the upgrade, be sure to open this file again and change the
303 * TRUE back to a FALSE!
304 */
305$settings['update_free_access'] = FALSE;
306
307/**
308 * External access proxy settings:
309 *
310 * If your site must access the Internet via a web proxy then you can enter the
311 * proxy settings here. Set the full URL of the proxy, including the port, in
312 * variables:
313 * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP
314 *   requests.
315 * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS
316 *   requests.
317 * You can pass in the user name and password for basic authentication in the
318 * URLs in these settings.
319 *
320 * You can also define an array of host names that can be accessed directly,
321 * bypassing the proxy, in $settings['http_client_config']['proxy']['no'].
322 */
323# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080';
324# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080';
325# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost'];
326
327/**
328 * Reverse Proxy Configuration:
329 *
330 * Reverse proxy servers are often used to enhance the performance
331 * of heavily visited sites and may also provide other site caching,
332 * security, or encryption benefits. In an environment where Drupal
333 * is behind a reverse proxy, the real IP address of the client should
334 * be determined such that the correct client IP address is available
335 * to Drupal's logging, statistics, and access management systems. In
336 * the most simple scenario, the proxy server will add an
337 * X-Forwarded-For header to the request that contains the client IP
338 * address. However, HTTP headers are vulnerable to spoofing, where a
339 * malicious client could bypass restrictions by setting the
340 * X-Forwarded-For header directly. Therefore, Drupal's proxy
341 * configuration requires the IP addresses of all remote proxies to be
342 * specified in $settings['reverse_proxy_addresses'] to work correctly.
343 *
344 * Enable this setting to get Drupal to determine the client IP from
345 * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
346 * If you are unsure about this setting, do not have a reverse proxy,
347 * or Drupal operates in a shared hosting environment, this setting
348 * should remain commented out.
349 *
350 * In order for this setting to be used you must specify every possible
351 * reverse proxy IP address in $settings['reverse_proxy_addresses'].
352 * If a complete list of reverse proxies is not available in your
353 * environment (for example, if you use a CDN) you may set the
354 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
355 * Be aware, however, that it is likely that this would allow IP
356 * address spoofing unless more advanced precautions are taken.
357 */
358# $settings['reverse_proxy'] = TRUE;
359
360/**
361 * Specify every reverse proxy IP address in your environment.
362 * This setting is required if $settings['reverse_proxy'] is TRUE.
363 */
364# $settings['reverse_proxy_addresses'] = ['a.b.c.d', ...];
365
366/**
367 * Set this value if your proxy server sends the client IP in a header
368 * other than X-Forwarded-For.
369 */
370# $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP';
371
372/**
373 * Set this value if your proxy server sends the client protocol in a header
374 * other than X-Forwarded-Proto.
375 */
376# $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO';
377
378/**
379 * Set this value if your proxy server sends the client protocol in a header
380 * other than X-Forwarded-Host.
381 */
382# $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST';
383
384/**
385 * Set this value if your proxy server sends the client protocol in a header
386 * other than X-Forwarded-Port.
387 */
388# $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT';
389
390/**
391 * Set this value if your proxy server sends the client protocol in a header
392 * other than Forwarded.
393 */
394# $settings['reverse_proxy_forwarded_header'] = 'FORWARDED';
395
396/**
397 * Page caching:
398 *
399 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
400 * views. This tells a HTTP proxy that it may return a page from its local
401 * cache without contacting the web server, if the user sends the same Cookie
402 * header as the user who originally requested the cached page. Without "Vary:
403 * Cookie", authenticated users would also be served the anonymous page from
404 * the cache. If the site has mostly anonymous users except a few known
405 * editors/administrators, the Vary header can be omitted. This allows for
406 * better caching in HTTP proxies (including reverse proxies), i.e. even if
407 * clients send different cookies, they still get content served from the cache.
408 * However, authenticated users should access the site directly (i.e. not use an
409 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
410 * getting cached pages from the proxy.
411 */
412# $settings['omit_vary_cookie'] = TRUE;
413
414
415/**
416 * Cache TTL for client error (4xx) responses.
417 *
418 * Items cached per-URL tend to result in a large number of cache items, and
419 * this can be problematic on 404 pages which by their nature are unbounded. A
420 * fixed TTL can be set for these items, defaulting to one hour, so that cache
421 * backends which do not support LRU can purge older entries. To disable caching
422 * of client error responses set the value to 0. Currently applies only to
423 * page_cache module.
424 */
425# $settings['cache_ttl_4xx'] = 3600;
426
427/**
428 * Expiration of cached forms.
429 *
430 * Drupal's Form API stores details of forms in a cache and these entries are
431 * kept for at least 6 hours by default. Expired entries are cleared by cron.
432 *
433 * @see \Drupal\Core\Form\FormCache::setCache()
434 */
435# $settings['form_cache_expiration'] = 21600;
436
437/**
438 * Class Loader.
439 *
440 * If the APC extension is detected, the Symfony APC class loader is used for
441 * performance reasons. Detection can be prevented by setting
442 * class_loader_auto_detect to false, as in the example below.
443 */
444# $settings['class_loader_auto_detect'] = FALSE;
445
446/*
447 * If the APC extension is not detected, either because APC is missing or
448 * because auto-detection has been disabled, auto-loading falls back to
449 * Composer's ClassLoader, which is good for development as it does not break
450 * when code is moved in the file system. You can also decorate the base class
451 * loader with another cached solution than the Symfony APC class loader, as
452 * all production sites should have a cached class loader of some sort enabled.
453 *
454 * To do so, you may decorate and replace the local $class_loader variable. For
455 * example, to use Symfony's APC class loader without automatic detection,
456 * uncomment the code below.
457 */
458/*
459if ($settings['hash_salt']) {
460  $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
461  $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
462  unset($prefix);
463  $class_loader->unregister();
464  $apc_loader->register();
465  $class_loader = $apc_loader;
466}
467*/
468
469/**
470 * Authorized file system operations:
471 *
472 * The Update Manager module included with Drupal provides a mechanism for
473 * site administrators to securely install missing updates for the site
474 * directly through the web user interface. On securely-configured servers,
475 * the Update manager will require the administrator to provide SSH or FTP
476 * credentials before allowing the installation to proceed; this allows the
477 * site to update the new files as the user who owns all the Drupal files,
478 * instead of as the user the webserver is running as. On servers where the
479 * webserver user is itself the owner of the Drupal files, the administrator
480 * will not be prompted for SSH or FTP credentials (note that these server
481 * setups are common on shared hosting, but are inherently insecure).
482 *
483 * Some sites might wish to disable the above functionality, and only update
484 * the code directly via SSH or FTP themselves. This setting completely
485 * disables all functionality related to these authorized file operations.
486 *
487 * @see https://www.drupal.org/node/244924
488 *
489 * Remove the leading hash signs to disable.
490 */
491# $settings['allow_authorize_operations'] = FALSE;
492
493/**
494 * Default mode for directories and files written by Drupal.
495 *
496 * Value should be in PHP Octal Notation, with leading zero.
497 */
498# $settings['file_chmod_directory'] = 0775;
499# $settings['file_chmod_file'] = 0664;
500
501/**
502 * Public file base URL:
503 *
504 * An alternative base URL to be used for serving public files. This must
505 * include any leading directory path.
506 *
507 * A different value from the domain used by Drupal to be used for accessing
508 * public files. This can be used for a simple CDN integration, or to improve
509 * security by serving user-uploaded files from a different domain or subdomain
510 * pointing to the same server. Do not include a trailing slash.
511 */
512# $settings['file_public_base_url'] = 'http://downloads.example.com/files';
513
514/**
515 * Public file path:
516 *
517 * A local file system path where public files will be stored. This directory
518 * must exist and be writable by Drupal. This directory must be relative to
519 * the Drupal installation directory and be accessible over the web.
520 */
521# $settings['file_public_path'] = 'sites/default/files';
522
523/**
524 * Private file path:
525 *
526 * A local file system path where private files will be stored. This directory
527 * must be absolute, outside of the Drupal installation directory and not
528 * accessible over the web.
529 *
530 * Note: Caches need to be cleared when this value is changed to make the
531 * private:// stream wrapper available to the system.
532 *
533 * See https://www.drupal.org/documentation/modules/file for more information
534 * about securing private files.
535 */
536# $settings['file_private_path'] = '';
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 * Active configuration settings.
600 *
601 * By default, the active configuration is stored in the database in the
602 * {config} table. To use a different storage mechanism for the active
603 * configuration, do the following prior to installing:
604 * - Create an "active" directory and declare its path in $config_directories
605 *   as explained under the 'Location of the site configuration files' section
606 *   above in this file. To enhance security, you can declare a path that is
607 *   outside your document root.
608 * - Override the 'bootstrap_config_storage' setting here. It must be set to a
609 *   callable that returns an object that implements
610 *   \Drupal\Core\Config\StorageInterface.
611 * - Override the service definition 'config.storage.active'. Put this
612 *   override in a services.yml file in the same directory as settings.php
613 *   (definitions in this file will override service definition defaults).
614 */
615# $settings['bootstrap_config_storage'] = ['Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage'];
616
617/**
618 * Configuration overrides.
619 *
620 * To globally override specific configuration values for this site,
621 * set them here. You usually don't need to use this feature. This is
622 * useful in a configuration file for a vhost or directory, rather than
623 * the default settings.php.
624 *
625 * Note that any values you provide in these variable overrides will not be
626 * viewable from the Drupal administration interface. The administration
627 * interface displays the values stored in configuration so that you can stage
628 * changes to other environments that don't have the overrides.
629 *
630 * There are particular configuration values that are risky to override. For
631 * example, overriding the list of installed modules in 'core.extension' is not
632 * supported as module install or uninstall has not occurred. Other examples
633 * include field storage configuration, because it has effects on database
634 * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
635 * a way that is not config override aware. Also, note that changing
636 * configuration values in settings.php will not fire any of the configuration
637 * change events.
638 */
639# $config['system.file']['path']['temporary'] = '/tmp';
640# $config['system.site']['name'] = 'My Drupal site';
641# $config['system.theme']['default'] = 'stark';
642# $config['user.settings']['anonymous'] = 'Visitor';
643
644/**
645 * Fast 404 pages:
646 *
647 * Drupal can generate fully themed 404 pages. However, some of these responses
648 * are for images or other resource files that are not displayed to the user.
649 * This can waste bandwidth, and also generate server load.
650 *
651 * The options below return a simple, fast 404 page for URLs matching a
652 * specific pattern:
653 * - $config['system.performance']['fast_404']['exclude_paths']: A regular
654 *   expression to match paths to exclude, such as images generated by image
655 *   styles, or dynamically-resized images. The default pattern provided below
656 *   also excludes the private file system. If you need to add more paths, you
657 *   can add '|path' to the expression.
658 * - $config['system.performance']['fast_404']['paths']: A regular expression to
659 *   match paths that should return a simple 404 page, rather than the fully
660 *   themed 404 page. If you don't have any aliases ending in htm or html you
661 *   can add '|s?html?' to the expression.
662 * - $config['system.performance']['fast_404']['html']: The html to return for
663 *   simple 404 pages.
664 *
665 * Remove the leading hash signs if you would like to alter this functionality.
666 */
667# $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
668# $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
669# $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>';
670
671/**
672 * Load services definition file.
673 */
674$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
675
676/**
677 * Override the default service container class.
678 *
679 * This is useful for example to trace the service container for performance
680 * tracking purposes, for testing a service container with an error condition or
681 * to test a service container that throws an exception.
682 */
683# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
684
685/**
686 * Override the default yaml parser class.
687 *
688 * Provide a fully qualified class name here if you would like to provide an
689 * alternate implementation YAML parser. The class must implement the
690 * \Drupal\Component\Serialization\SerializationInterface interface.
691 */
692# $settings['yaml_parser_class'] = NULL;
693
694/**
695 * Trusted host configuration.
696 *
697 * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
698 * header spoofing.
699 *
700 * To enable the trusted host mechanism, you enable your allowable hosts
701 * in $settings['trusted_host_patterns']. This should be an array of regular
702 * expression patterns, without delimiters, representing the hosts you would
703 * like to allow.
704 *
705 * For example:
706 * @code
707 * $settings['trusted_host_patterns'] = array(
708 *   '^www\.example\.com$',
709 * );
710 * @endcode
711 * will allow the site to only run from www.example.com.
712 *
713 * If you are running multisite, or if you are running your site from
714 * different domain names (eg, you don't redirect http://www.example.com to
715 * http://example.com), you should specify all of the host patterns that are
716 * allowed by your site.
717 *
718 * For example:
719 * @code
720 * $settings['trusted_host_patterns'] = array(
721 *   '^example\.com$',
722 *   '^.+\.example\.com$',
723 *   '^example\.org$',
724 *   '^.+\.example\.org$',
725 * );
726 * @endcode
727 * will allow the site to run off of all variants of example.com and
728 * example.org, with all subdomains included.
729 */
730
731/**
732 * The default list of directories that will be ignored by Drupal's file API.
733 *
734 * By default ignore node_modules and bower_components folders to avoid issues
735 * with common frontend tools and recursive scanning of directories looking for
736 * extensions.
737 *
738 * @see file_scan_directory()
739 * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory()
740 */
741$settings['file_scan_ignore_directories'] = [
742    'node_modules',
743    'bower_components',
744];
745
746/**
747 * The default number of entities to update in a batch process.
748 *
749 * This is used by update and post-update functions that need to go through and
750 * change all the entities on a site, so it is useful to increase this number
751 * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a
752 * larger number of entities to be processed in a single batch run.
753 */
754$settings['entity_update_batch_size'] = 50;
755
756/**
757 * Load local development override configuration, if available.
758 *
759 * Use settings.local.php to override variables on secondary (staging,
760 * development, etc) installations of this site. Typically used to disable
761 * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
762 * other things that should not happen on development and testing sites.
763 *
764 * Keep this code block at the end of this file to take full effect.
765 */
766if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
767    include $app_root . '/' . $site_path . '/settings.local.php';
768}
769$config_directories['sync'] = '../config/sync';
770$databases['default']['default'] = array(
771    'database' => 'dibujantes',
772    'username' => 'root',
773    'password' => 'canesblink182',
774    'prefix' => '',
775    'host' => '127.0.0.1',
776    'port' => '3306',
777    'namespace' => 'Drupal\\Core\\Database\\Driver\\mysql',
778    'driver' => 'mysql',
779);
780$config['config_split.config_split.dev']['status'] = TRUE;
781$settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml';
782$config['system.performance']['css']['preprocess'] = FALSE;
783$config['system.performance']['js']['preprocess'] = FALSE;
784$settings['cache']['bins']['render'] = 'cache.backend.null';
785$settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.null';