5 * Drupal site-specific configuration file.
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
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.
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.
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:
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
33 * - sites/8080.www.drupal.org.mysite
34 * - sites/www.drupal.org.mysite
35 * - sites/drupal.org.mysite
38 * - sites/8080.www.drupal.org
39 * - sites/www.drupal.org
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/.
50 * @see example.sites.php
51 * @see \Drupal\Core\DrupalKernel::getSitePath()
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.
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.
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.
73 * The next section describes how to customize the $databases array for more
77 * $databases['default']['default'] = array (
78 * 'database' => 'databasename',
79 * 'username' => 'sqlusername',
80 * 'password' => 'sqlpassword',
81 * 'host' => 'localhost',
83 * 'driver' => 'mysql',
85 * 'collation' => 'utf8mb4_general_ci',
92 * Customizing database settings.
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
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.
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
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'
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).
122 * The general format for the $databases array is as follows:
124 * $databases['default']['default'] = $info_array;
125 * $databases['default']['replica'][] = $info_array;
126 * $databases['default']['replica'][] = $info_array;
127 * $databases['extra']['default'] = $info_array;
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
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 ''.
143 * To have all database names prefixed, set 'prefix' as a string:
145 * 'prefix' => 'main_',
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:
153 * 'default' => 'main_',
154 * 'users' => 'shared_',
155 * 'sessions' => 'shared_',
156 * 'role' => 'shared_',
157 * 'authmap' => 'shared_',
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
167 * 'default' => 'main.',
168 * 'users' => 'shared.',
169 * 'sessions' => 'shared.',
170 * 'role' => 'shared.',
171 * 'authmap' => 'shared.',
174 * NOTE: MySQL and SQLite's definition of a schema is a database.
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:
181 * $databases['default']['default'] = array(
182 * 'init_commands' => array(
183 * 'big_selects' => 'SET SQL_BIG_SELECTS=1',
186 * PDO::ATTR_TIMEOUT => 5,
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.
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()
201 * Sample Database configuration format for PostgreSQL (pgsql):
203 * $databases['default']['default'] = array(
204 * 'driver' => 'pgsql',
205 * 'database' => 'databasename',
206 * 'username' => 'sqlusername',
207 * 'password' => 'sqlpassword',
208 * 'host' => 'localhost',
213 * Sample Database configuration format for SQLite (sqlite):
215 * $databases['default']['default'] = array(
216 * 'driver' => 'sqlite',
217 * 'database' => '/path/to/databasefilename',
223 * Location of the site configuration files.
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).
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.
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.
242 * $config_directories = array(
243 * CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot',
247 $config_directories = array();
252 * $settings contains environment-specific configuration, such as the files
253 * directory and reverse proxy address, and temporary configuration, such as
254 * security overrides.
256 * @see \Drupal\Core\Site\Settings::get()
260 * The active installation profile.
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
267 * @see install_select_profile()
269 # $settings['install_profile'] = '';
272 * Salt for one-time login links, cancel links, form tokens, etc.
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.
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.
285 * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
288 $settings['hash_salt'] = '';
291 * Deployment identifier.
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.
298 # $settings['deployment_identifier'] = \Drupal::VERSION;
301 * Access control for update.php script.
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!
311 $settings['update_free_access'] = FALSE;
314 * External access proxy settings:
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
319 * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP
321 * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS
323 * You can pass in the user name and password for basic authentication in the
324 * URLs in these settings.
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'].
329 # $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080';
330 # $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080';
331 # $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost'];
334 * Reverse Proxy Configuration:
336 * Reverse proxy servers are often used to enhance the performance
337 * of heavily visited sites and may also provide other site caching,
338 * security, or encryption benefits. In an environment where Drupal
339 * is behind a reverse proxy, the real IP address of the client should
340 * be determined such that the correct client IP address is available
341 * to Drupal's logging, statistics, and access management systems. In
342 * the most simple scenario, the proxy server will add an
343 * X-Forwarded-For header to the request that contains the client IP
344 * address. However, HTTP headers are vulnerable to spoofing, where a
345 * malicious client could bypass restrictions by setting the
346 * X-Forwarded-For header directly. Therefore, Drupal's proxy
347 * configuration requires the IP addresses of all remote proxies to be
348 * specified in $settings['reverse_proxy_addresses'] to work correctly.
350 * Enable this setting to get Drupal to determine the client IP from
351 * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
352 * If you are unsure about this setting, do not have a reverse proxy,
353 * or Drupal operates in a shared hosting environment, this setting
354 * should remain commented out.
356 * In order for this setting to be used you must specify every possible
357 * reverse proxy IP address in $settings['reverse_proxy_addresses'].
358 * If a complete list of reverse proxies is not available in your
359 * environment (for example, if you use a CDN) you may set the
360 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
361 * Be aware, however, that it is likely that this would allow IP
362 * address spoofing unless more advanced precautions are taken.
364 # $settings['reverse_proxy'] = TRUE;
367 * Specify every reverse proxy IP address in your environment.
368 * This setting is required if $settings['reverse_proxy'] is TRUE.
370 # $settings['reverse_proxy_addresses'] = array('a.b.c.d', ...);
373 * Set this value if your proxy server sends the client IP in a header
374 * other than X-Forwarded-For.
376 # $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP';
379 * Set this value if your proxy server sends the client protocol in a header
380 * other than X-Forwarded-Proto.
382 # $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO';
385 * Set this value if your proxy server sends the client protocol in a header
386 * other than X-Forwarded-Host.
388 # $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST';
391 * Set this value if your proxy server sends the client protocol in a header
392 * other than X-Forwarded-Port.
394 # $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT';
397 * Set this value if your proxy server sends the client protocol in a header
398 * other than Forwarded.
400 # $settings['reverse_proxy_forwarded_header'] = 'FORWARDED';
405 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
406 * views. This tells a HTTP proxy that it may return a page from its local
407 * cache without contacting the web server, if the user sends the same Cookie
408 * header as the user who originally requested the cached page. Without "Vary:
409 * Cookie", authenticated users would also be served the anonymous page from
410 * the cache. If the site has mostly anonymous users except a few known
411 * editors/administrators, the Vary header can be omitted. This allows for
412 * better caching in HTTP proxies (including reverse proxies), i.e. even if
413 * clients send different cookies, they still get content served from the cache.
414 * However, authenticated users should access the site directly (i.e. not use an
415 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
416 * getting cached pages from the proxy.
418 # $settings['omit_vary_cookie'] = TRUE;
422 * Cache TTL for client error (4xx) responses.
424 * Items cached per-URL tend to result in a large number of cache items, and
425 * this can be problematic on 404 pages which by their nature are unbounded. A
426 * fixed TTL can be set for these items, defaulting to one hour, so that cache
427 * backends which do not support LRU can purge older entries. To disable caching
428 * of client error responses set the value to 0. Currently applies only to
431 # $settings['cache_ttl_4xx'] = 3600;
437 * If the APC extension is detected, the Symfony APC class loader is used for
438 * performance reasons. Detection can be prevented by setting
439 * class_loader_auto_detect to false, as in the example below.
441 # $settings['class_loader_auto_detect'] = FALSE;
444 * If the APC extension is not detected, either because APC is missing or
445 * because auto-detection has been disabled, auto-loading falls back to
446 * Composer's ClassLoader, which is good for development as it does not break
447 * when code is moved in the file system. You can also decorate the base class
448 * loader with another cached solution than the Symfony APC class loader, as
449 * all production sites should have a cached class loader of some sort enabled.
451 * To do so, you may decorate and replace the local $class_loader variable. For
452 * example, to use Symfony's APC class loader without automatic detection,
453 * uncomment the code below.
456 if ($settings['hash_salt']) {
457 $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
458 $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
460 $class_loader->unregister();
461 $apc_loader->register();
462 $class_loader = $apc_loader;
467 * Authorized file system operations:
469 * The Update Manager module included with Drupal provides a mechanism for
470 * site administrators to securely install missing updates for the site
471 * directly through the web user interface. On securely-configured servers,
472 * the Update manager will require the administrator to provide SSH or FTP
473 * credentials before allowing the installation to proceed; this allows the
474 * site to update the new files as the user who owns all the Drupal files,
475 * instead of as the user the webserver is running as. On servers where the
476 * webserver user is itself the owner of the Drupal files, the administrator
477 * will not be prompted for SSH or FTP credentials (note that these server
478 * setups are common on shared hosting, but are inherently insecure).
480 * Some sites might wish to disable the above functionality, and only update
481 * the code directly via SSH or FTP themselves. This setting completely
482 * disables all functionality related to these authorized file operations.
484 * @see https://www.drupal.org/node/244924
486 * Remove the leading hash signs to disable.
488 # $settings['allow_authorize_operations'] = FALSE;
491 * Default mode for directories and files written by Drupal.
493 * Value should be in PHP Octal Notation, with leading zero.
495 # $settings['file_chmod_directory'] = 0775;
496 # $settings['file_chmod_file'] = 0664;
499 * Public file base URL:
501 * An alternative base URL to be used for serving public files. This must
502 * include any leading directory path.
504 * A different value from the domain used by Drupal to be used for accessing
505 * public files. This can be used for a simple CDN integration, or to improve
506 * security by serving user-uploaded files from a different domain or subdomain
507 * pointing to the same server. Do not include a trailing slash.
509 # $settings['file_public_base_url'] = 'http://downloads.example.com/files';
514 * A local file system path where public files will be stored. This directory
515 * must exist and be writable by Drupal. This directory must be relative to
516 * the Drupal installation directory and be accessible over the web.
518 # $settings['file_public_path'] = 'sites/default/files';
523 * A local file system path where private files will be stored. This directory
524 * must be absolute, outside of the Drupal installation directory and not
525 * accessible over the web.
527 * Note: Caches need to be cleared when this value is changed to make the
528 * private:// stream wrapper available to the system.
530 * See https://www.drupal.org/documentation/modules/file for more information
531 * about securing private files.
533 # $settings['file_private_path'] = '';
536 * Session write interval:
538 * Set the minimum interval between each session write to database.
539 * For performance reasons it defaults to 180.
541 # $settings['session_write_interval'] = 180;
546 * To override specific strings on your site with or without enabling the Locale
547 * module, add an entry to this list. This functionality allows you to change
548 * a small number of your site's default English language interface strings.
550 * Remove the leading hash signs to enable.
552 * The "en" part of the variable name, is dynamic and can be any langcode of
553 * any added language. (eg locale_custom_strings_de for german).
555 # $settings['locale_custom_strings_en'][''] = array(
556 # 'forum' => 'Discussion board',
557 # '@count min' => '@count minutes',
561 * A custom theme for the offline page:
563 * This applies when the site is explicitly set to maintenance mode through the
564 * administration page or when the database is inactive due to an error.
565 * The template file should also be copied into the theme. It is located inside
566 * 'core/modules/system/templates/maintenance-page.html.twig'.
568 * Note: This setting does not apply to installation and update pages.
570 # $settings['maintenance_theme'] = 'bartik';
575 * To see what PHP settings are possible, including whether they can be set at
576 * runtime (by using ini_set()), read the PHP documentation:
577 * http://php.net/manual/ini.list.php
578 * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime
579 * settings and the .htaccess file for non-runtime settings.
580 * Settings defined there should not be duplicated here so as to avoid conflict
585 * If you encounter a situation where users post a large amount of text, and
586 * the result is stripped out upon viewing but can still be edited, Drupal's
587 * output filter may not have sufficient memory to process it. If you
588 * experience this issue, you may wish to uncomment the following two lines
589 * and increase the limits of these variables. For more information, see
590 * http://php.net/manual/pcre.configuration.php.
592 # ini_set('pcre.backtrack_limit', 200000);
593 # ini_set('pcre.recursion_limit', 200000);
596 * Active configuration settings.
598 * By default, the active configuration is stored in the database in the
599 * {config} table. To use a different storage mechanism for the active
600 * configuration, do the following prior to installing:
601 * - Create an "active" directory and declare its path in $config_directories
602 * as explained under the 'Location of the site configuration files' section
603 * above in this file. To enhance security, you can declare a path that is
604 * outside your document root.
605 * - Override the 'bootstrap_config_storage' setting here. It must be set to a
606 * callable that returns an object that implements
607 * \Drupal\Core\Config\StorageInterface.
608 * - Override the service definition 'config.storage.active'. Put this
609 * override in a services.yml file in the same directory as settings.php
610 * (definitions in this file will override service definition defaults).
612 # $settings['bootstrap_config_storage'] = array('Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage');
615 * Configuration overrides.
617 * To globally override specific configuration values for this site,
618 * set them here. You usually don't need to use this feature. This is
619 * useful in a configuration file for a vhost or directory, rather than
620 * the default settings.php.
622 * Note that any values you provide in these variable overrides will not be
623 * viewable from the Drupal administration interface. The administration
624 * interface displays the values stored in configuration so that you can stage
625 * changes to other environments that don't have the overrides.
627 * There are particular configuration values that are risky to override. For
628 * example, overriding the list of installed modules in 'core.extension' is not
629 * supported as module install or uninstall has not occurred. Other examples
630 * include field storage configuration, because it has effects on database
631 * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
632 * a way that is not config override aware. Also, note that changing
633 * configuration values in settings.php will not fire any of the configuration
636 # $config['system.site']['name'] = 'My Drupal site';
637 # $config['system.theme']['default'] = 'stark';
638 # $config['user.settings']['anonymous'] = 'Visitor';
643 * Drupal can generate fully themed 404 pages. However, some of these responses
644 * are for images or other resource files that are not displayed to the user.
645 * This can waste bandwidth, and also generate server load.
647 * The options below return a simple, fast 404 page for URLs matching a
649 * - $config['system.performance']['fast_404']['exclude_paths']: A regular
650 * expression to match paths to exclude, such as images generated by image
651 * styles, or dynamically-resized images. The default pattern provided below
652 * also excludes the private file system. If you need to add more paths, you
653 * can add '|path' to the expression.
654 * - $config['system.performance']['fast_404']['paths']: A regular expression to
655 * match paths that should return a simple 404 page, rather than the fully
656 * themed 404 page. If you don't have any aliases ending in htm or html you
657 * can add '|s?html?' to the expression.
658 * - $config['system.performance']['fast_404']['html']: The html to return for
661 * Remove the leading hash signs if you would like to alter this functionality.
663 # $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
664 # $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
665 # $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>';
668 * Load services definition file.
670 $settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
673 * Override the default service container class.
675 * This is useful for example to trace the service container for performance
676 * tracking purposes, for testing a service container with an error condition or
677 * to test a service container that throws an exception.
679 # $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
682 * Override the default yaml parser class.
684 * Provide a fully qualified class name here if you would like to provide an
685 * alternate implementation YAML parser. The class must implement the
686 * \Drupal\Component\Serialization\SerializationInterface interface.
688 # $settings['yaml_parser_class'] = NULL;
691 * Trusted host configuration.
693 * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
696 * To enable the trusted host mechanism, you enable your allowable hosts
697 * in $settings['trusted_host_patterns']. This should be an array of regular
698 * expression patterns, without delimiters, representing the hosts you would
703 * $settings['trusted_host_patterns'] = array(
704 * '^www\.example\.com$',
707 * will allow the site to only run from www.example.com.
709 * If you are running multisite, or if you are running your site from
710 * different domain names (eg, you don't redirect http://www.example.com to
711 * http://example.com), you should specify all of the host patterns that are
712 * allowed by your site.
716 * $settings['trusted_host_patterns'] = array(
718 * '^.+\.example\.com$',
720 * '^.+\.example\.org$',
723 * will allow the site to run off of all variants of example.com and
724 * example.org, with all subdomains included.
728 * The default list of directories that will be ignored by Drupal's file API.
730 * By default ignore node_modules and bower_components folders to avoid issues
731 * with common frontend tools and recursive scanning of directories looking for
734 * @see file_scan_directory()
735 * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory()
737 $settings['file_scan_ignore_directories'] = [
743 * Load local development override configuration, if available.
745 * Use settings.local.php to override variables on secondary (staging,
746 * development, etc) installations of this site. Typically used to disable
747 * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
748 * other things that should not happen on development and testing sites.
750 * Keep this code block at the end of this file to take full effect.
753 # if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
754 # include $app_root . '/' . $site_path . '/settings.local.php';