CHHTMJe6

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