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