Chris@0: 'databasename',
Chris@0: * 'username' => 'sqlusername',
Chris@0: * 'password' => 'sqlpassword',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'port' => '3306',
Chris@0: * 'driver' => 'mysql',
Chris@0: * 'prefix' => '',
Chris@0: * 'collation' => 'utf8mb4_general_ci',
Chris@0: * );
Chris@0: * @endcode
Chris@0: */
Chris@0: $databases = array();
Chris@0:
Chris@0: /**
Chris@0: * Customizing database settings.
Chris@0: *
Chris@0: * Many of the values of the $databases array can be customized for your
Chris@0: * particular database system. Refer to the sample in the section above as a
Chris@0: * starting point.
Chris@0: *
Chris@0: * The "driver" property indicates what Drupal database driver the
Chris@0: * connection should use. This is usually the same as the name of the
Chris@0: * database type, such as mysql or sqlite, but not always. The other
Chris@0: * properties will vary depending on the driver. For SQLite, you must
Chris@0: * specify a database file name in a directory that is writable by the
Chris@0: * webserver. For most other drivers, you must specify a
Chris@0: * username, password, host, and database name.
Chris@0: *
Chris@0: * Transaction support is enabled by default for all drivers that support it,
Chris@0: * including MySQL. To explicitly disable it, set the 'transactions' key to
Chris@0: * FALSE.
Chris@0: * Note that some configurations of MySQL, such as the MyISAM engine, don't
Chris@0: * support it and will proceed silently even if enabled. If you experience
Chris@0: * transaction related crashes with such configuration, set the 'transactions'
Chris@0: * key to FALSE.
Chris@0: *
Chris@0: * For each database, you may optionally specify multiple "target" databases.
Chris@0: * A target database allows Drupal to try to send certain queries to a
Chris@0: * different database if it can but fall back to the default connection if not.
Chris@0: * That is useful for primary/replica replication, as Drupal may try to connect
Chris@0: * to a replica server when appropriate and if one is not available will simply
Chris@0: * fall back to the single primary server (The terms primary/replica are
Chris@0: * traditionally referred to as master/slave in database server documentation).
Chris@0: *
Chris@0: * The general format for the $databases array is as follows:
Chris@0: * @code
Chris@0: * $databases['default']['default'] = $info_array;
Chris@0: * $databases['default']['replica'][] = $info_array;
Chris@0: * $databases['default']['replica'][] = $info_array;
Chris@0: * $databases['extra']['default'] = $info_array;
Chris@0: * @endcode
Chris@0: *
Chris@0: * In the above example, $info_array is an array of settings described above.
Chris@0: * The first line sets a "default" database that has one primary database
Chris@0: * (the second level default). The second and third lines create an array
Chris@0: * of potential replica databases. Drupal will select one at random for a given
Chris@0: * request as needed. The fourth line creates a new database with a name of
Chris@0: * "extra".
Chris@0: *
Chris@0: * You can optionally set prefixes for some or all database table names
Chris@0: * by using the 'prefix' setting. If a prefix is specified, the table
Chris@0: * name will be prepended with its value. Be sure to use valid database
Chris@0: * characters only, usually alphanumeric and underscore. If no prefixes
Chris@0: * are desired, leave it as an empty string ''.
Chris@0: *
Chris@0: * To have all database names prefixed, set 'prefix' as a string:
Chris@0: * @code
Chris@0: * 'prefix' => 'main_',
Chris@0: * @endcode
Chris@0: *
Chris@0: * Per-table prefixes are deprecated as of Drupal 8.2, and will be removed in
Chris@0: * Drupal 9.0. After that, only a single prefix for all tables will be
Chris@0: * supported.
Chris@0: *
Chris@0: * To provide prefixes for specific tables, set 'prefix' as an array.
Chris@0: * The array's keys are the table names and the values are the prefixes.
Chris@0: * The 'default' element is mandatory and holds the prefix for any tables
Chris@0: * not specified elsewhere in the array. Example:
Chris@0: * @code
Chris@0: * 'prefix' => array(
Chris@0: * 'default' => 'main_',
Chris@0: * 'users' => 'shared_',
Chris@0: * 'sessions' => 'shared_',
Chris@0: * 'role' => 'shared_',
Chris@0: * 'authmap' => 'shared_',
Chris@0: * ),
Chris@0: * @endcode
Chris@0: * You can also use a reference to a schema/database as a prefix. This may be
Chris@0: * useful if your Drupal installation exists in a schema that is not the default
Chris@0: * or you want to access several databases from the same code base at the same
Chris@0: * time.
Chris@0: * Example:
Chris@0: * @code
Chris@0: * 'prefix' => array(
Chris@0: * 'default' => 'main.',
Chris@0: * 'users' => 'shared.',
Chris@0: * 'sessions' => 'shared.',
Chris@0: * 'role' => 'shared.',
Chris@0: * 'authmap' => 'shared.',
Chris@0: * );
Chris@0: * @endcode
Chris@0: * NOTE: MySQL and SQLite's definition of a schema is a database.
Chris@0: *
Chris@0: * Advanced users can add or override initial commands to execute when
Chris@0: * connecting to the database server, as well as PDO connection settings. For
Chris@0: * example, to enable MySQL SELECT queries to exceed the max_join_size system
Chris@0: * variable, and to reduce the database connection timeout to 5 seconds:
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'init_commands' => array(
Chris@0: * 'big_selects' => 'SET SQL_BIG_SELECTS=1',
Chris@0: * ),
Chris@0: * 'pdo' => array(
Chris@0: * PDO::ATTR_TIMEOUT => 5,
Chris@0: * ),
Chris@0: * );
Chris@0: * @endcode
Chris@0: *
Chris@0: * WARNING: The above defaults are designed for database portability. Changing
Chris@0: * them may cause unexpected behavior, including potential data loss. See
Chris@0: * https://www.drupal.org/developing/api/database/configuration for more
Chris@0: * information on these defaults and the potential issues.
Chris@0: *
Chris@0: * More details can be found in the constructor methods for each driver:
Chris@0: * - \Drupal\Core\Database\Driver\mysql\Connection::__construct()
Chris@0: * - \Drupal\Core\Database\Driver\pgsql\Connection::__construct()
Chris@0: * - \Drupal\Core\Database\Driver\sqlite\Connection::__construct()
Chris@0: *
Chris@0: * Sample Database configuration format for PostgreSQL (pgsql):
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'pgsql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'sqlusername',
Chris@0: * 'password' => 'sqlpassword',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'prefix' => '',
Chris@0: * );
Chris@0: * @endcode
Chris@0: *
Chris@0: * Sample Database configuration format for SQLite (sqlite):
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'sqlite',
Chris@0: * 'database' => '/path/to/databasefilename',
Chris@0: * );
Chris@0: * @endcode
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * Location of the site configuration files.
Chris@0: *
Chris@0: * The $config_directories array specifies the location of file system
Chris@0: * directories used for configuration data. On install, the "sync" directory is
Chris@0: * created. This is used for configuration imports. The "active" directory is
Chris@0: * not created by default since the default storage for active configuration is
Chris@0: * the database rather than the file system. (This can be changed. See "Active
Chris@0: * configuration settings" below).
Chris@0: *
Chris@0: * The default location for the "sync" directory is inside a randomly-named
Chris@0: * directory in the public files path. The setting below allows you to override
Chris@0: * the "sync" location.
Chris@0: *
Chris@0: * If you use files for the "active" configuration, you can tell the
Chris@0: * Configuration system where this directory is located by adding an entry with
Chris@0: * array key CONFIG_ACTIVE_DIRECTORY.
Chris@0: *
Chris@0: * Example:
Chris@0: * @code
Chris@0: * $config_directories = array(
Chris@0: * CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot',
Chris@0: * );
Chris@0: * @endcode
Chris@0: */
Chris@0: $config_directories = array();
Chris@0:
Chris@0: /**
Chris@0: * Settings:
Chris@0: *
Chris@0: * $settings contains environment-specific configuration, such as the files
Chris@0: * directory and reverse proxy address, and temporary configuration, such as
Chris@0: * security overrides.
Chris@0: *
Chris@0: * @see \Drupal\Core\Site\Settings::get()
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * The active installation profile.
Chris@0: *
Chris@0: * Changing this after installation is not recommended as it changes which
Chris@0: * directories are scanned during extension discovery. If this is set prior to
Chris@0: * installation this value will be rewritten according to the profile selected
Chris@0: * by the user.
Chris@0: *
Chris@0: * @see install_select_profile()
Chris@0: *
Chris@0: * @deprecated in Drupal 8.3.0 and will be removed before Drupal 9.0.0. The
Chris@0: * install profile is written to the core.extension configuration. If a
Chris@0: * service requires the install profile use the 'install_profile' container
Chris@0: * parameter. Functional code can use \Drupal::installProfile().
Chris@0: */
Chris@0: # $settings['install_profile'] = '';
Chris@0:
Chris@0: /**
Chris@0: * Salt for one-time login links, cancel links, form tokens, etc.
Chris@0: *
Chris@0: * This variable will be set to a random value by the installer. All one-time
Chris@0: * login links will be invalidated if the value is changed. Note that if your
Chris@0: * site is deployed on a cluster of web servers, you must ensure that this
Chris@0: * variable has the same value on each server.
Chris@0: *
Chris@0: * For enhanced security, you may set this variable to the contents of a file
Chris@0: * outside your document root; you should also ensure that this file is not
Chris@0: * stored with backups of your database.
Chris@0: *
Chris@0: * Example:
Chris@0: * @code
Chris@0: * $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
Chris@0: * @endcode
Chris@0: */
Chris@0: $settings['hash_salt'] = '';
Chris@0:
Chris@0: /**
Chris@0: * Deployment identifier.
Chris@0: *
Chris@0: * Drupal's dependency injection container will be automatically invalidated and
Chris@0: * rebuilt when the Drupal core version changes. When updating contributed or
Chris@0: * custom code that changes the container, changing this identifier will also
Chris@0: * allow the container to be invalidated as soon as code is deployed.
Chris@0: */
Chris@0: # $settings['deployment_identifier'] = \Drupal::VERSION;
Chris@0:
Chris@0: /**
Chris@0: * Access control for update.php script.
Chris@0: *
Chris@0: * If you are updating your Drupal installation using the update.php script but
Chris@0: * are not logged in using either an account with the "Administer software
Chris@0: * updates" permission or the site maintenance account (the account that was
Chris@0: * created during installation), you will need to modify the access check
Chris@0: * statement below. Change the FALSE to a TRUE to disable the access check.
Chris@0: * After finishing the upgrade, be sure to open this file again and change the
Chris@0: * TRUE back to a FALSE!
Chris@0: */
Chris@0: $settings['update_free_access'] = FALSE;
Chris@0:
Chris@0: /**
Chris@0: * External access proxy settings:
Chris@0: *
Chris@0: * If your site must access the Internet via a web proxy then you can enter the
Chris@0: * proxy settings here. Set the full URL of the proxy, including the port, in
Chris@0: * variables:
Chris@0: * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP
Chris@0: * requests.
Chris@0: * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS
Chris@0: * requests.
Chris@0: * You can pass in the user name and password for basic authentication in the
Chris@0: * URLs in these settings.
Chris@0: *
Chris@0: * You can also define an array of host names that can be accessed directly,
Chris@0: * bypassing the proxy, in $settings['http_client_config']['proxy']['no'].
Chris@0: */
Chris@0: # $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080';
Chris@0: # $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080';
Chris@0: # $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost'];
Chris@0:
Chris@0: /**
Chris@0: * Reverse Proxy Configuration:
Chris@0: *
Chris@0: * Reverse proxy servers are often used to enhance the performance
Chris@0: * of heavily visited sites and may also provide other site caching,
Chris@0: * security, or encryption benefits. In an environment where Drupal
Chris@0: * is behind a reverse proxy, the real IP address of the client should
Chris@0: * be determined such that the correct client IP address is available
Chris@0: * to Drupal's logging, statistics, and access management systems. In
Chris@0: * the most simple scenario, the proxy server will add an
Chris@0: * X-Forwarded-For header to the request that contains the client IP
Chris@0: * address. However, HTTP headers are vulnerable to spoofing, where a
Chris@0: * malicious client could bypass restrictions by setting the
Chris@0: * X-Forwarded-For header directly. Therefore, Drupal's proxy
Chris@0: * configuration requires the IP addresses of all remote proxies to be
Chris@0: * specified in $settings['reverse_proxy_addresses'] to work correctly.
Chris@0: *
Chris@0: * Enable this setting to get Drupal to determine the client IP from
Chris@0: * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
Chris@0: * If you are unsure about this setting, do not have a reverse proxy,
Chris@0: * or Drupal operates in a shared hosting environment, this setting
Chris@0: * should remain commented out.
Chris@0: *
Chris@0: * In order for this setting to be used you must specify every possible
Chris@0: * reverse proxy IP address in $settings['reverse_proxy_addresses'].
Chris@0: * If a complete list of reverse proxies is not available in your
Chris@0: * environment (for example, if you use a CDN) you may set the
Chris@0: * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
Chris@0: * Be aware, however, that it is likely that this would allow IP
Chris@0: * address spoofing unless more advanced precautions are taken.
Chris@0: */
Chris@0: # $settings['reverse_proxy'] = TRUE;
Chris@0:
Chris@0: /**
Chris@0: * Specify every reverse proxy IP address in your environment.
Chris@0: * This setting is required if $settings['reverse_proxy'] is TRUE.
Chris@0: */
Chris@0: # $settings['reverse_proxy_addresses'] = array('a.b.c.d', ...);
Chris@0:
Chris@0: /**
Chris@0: * Set this value if your proxy server sends the client IP in a header
Chris@0: * other than X-Forwarded-For.
Chris@0: */
Chris@0: # $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP';
Chris@0:
Chris@0: /**
Chris@0: * Set this value if your proxy server sends the client protocol in a header
Chris@0: * other than X-Forwarded-Proto.
Chris@0: */
Chris@0: # $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO';
Chris@0:
Chris@0: /**
Chris@0: * Set this value if your proxy server sends the client protocol in a header
Chris@0: * other than X-Forwarded-Host.
Chris@0: */
Chris@0: # $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST';
Chris@0:
Chris@0: /**
Chris@0: * Set this value if your proxy server sends the client protocol in a header
Chris@0: * other than X-Forwarded-Port.
Chris@0: */
Chris@0: # $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT';
Chris@0:
Chris@0: /**
Chris@0: * Set this value if your proxy server sends the client protocol in a header
Chris@0: * other than Forwarded.
Chris@0: */
Chris@0: # $settings['reverse_proxy_forwarded_header'] = 'FORWARDED';
Chris@0:
Chris@0: /**
Chris@0: * Page caching:
Chris@0: *
Chris@0: * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
Chris@0: * views. This tells a HTTP proxy that it may return a page from its local
Chris@0: * cache without contacting the web server, if the user sends the same Cookie
Chris@0: * header as the user who originally requested the cached page. Without "Vary:
Chris@0: * Cookie", authenticated users would also be served the anonymous page from
Chris@0: * the cache. If the site has mostly anonymous users except a few known
Chris@0: * editors/administrators, the Vary header can be omitted. This allows for
Chris@0: * better caching in HTTP proxies (including reverse proxies), i.e. even if
Chris@0: * clients send different cookies, they still get content served from the cache.
Chris@0: * However, authenticated users should access the site directly (i.e. not use an
Chris@0: * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
Chris@0: * getting cached pages from the proxy.
Chris@0: */
Chris@0: # $settings['omit_vary_cookie'] = TRUE;
Chris@0:
Chris@0:
Chris@0: /**
Chris@0: * Cache TTL for client error (4xx) responses.
Chris@0: *
Chris@0: * Items cached per-URL tend to result in a large number of cache items, and
Chris@0: * this can be problematic on 404 pages which by their nature are unbounded. A
Chris@0: * fixed TTL can be set for these items, defaulting to one hour, so that cache
Chris@0: * backends which do not support LRU can purge older entries. To disable caching
Chris@0: * of client error responses set the value to 0. Currently applies only to
Chris@0: * page_cache module.
Chris@0: */
Chris@0: # $settings['cache_ttl_4xx'] = 3600;
Chris@0:
Chris@0: /**
Chris@0: * Expiration of cached forms.
Chris@0: *
Chris@0: * Drupal's Form API stores details of forms in a cache and these entries are
Chris@0: * kept for at least 6 hours by default. Expired entries are cleared by cron.
Chris@0: *
Chris@0: * @see \Drupal\Core\Form\FormCache::setCache()
Chris@0: */
Chris@0: # $settings['form_cache_expiration'] = 21600;
Chris@0:
Chris@0: /**
Chris@0: * Class Loader.
Chris@0: *
Chris@0: * If the APC extension is detected, the Symfony APC class loader is used for
Chris@0: * performance reasons. Detection can be prevented by setting
Chris@0: * class_loader_auto_detect to false, as in the example below.
Chris@0: */
Chris@0: # $settings['class_loader_auto_detect'] = FALSE;
Chris@0:
Chris@0: /*
Chris@0: * If the APC extension is not detected, either because APC is missing or
Chris@0: * because auto-detection has been disabled, auto-loading falls back to
Chris@0: * Composer's ClassLoader, which is good for development as it does not break
Chris@0: * when code is moved in the file system. You can also decorate the base class
Chris@0: * loader with another cached solution than the Symfony APC class loader, as
Chris@0: * all production sites should have a cached class loader of some sort enabled.
Chris@0: *
Chris@0: * To do so, you may decorate and replace the local $class_loader variable. For
Chris@0: * example, to use Symfony's APC class loader without automatic detection,
Chris@0: * uncomment the code below.
Chris@0: */
Chris@0: /*
Chris@0: if ($settings['hash_salt']) {
Chris@0: $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
Chris@0: $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
Chris@0: unset($prefix);
Chris@0: $class_loader->unregister();
Chris@0: $apc_loader->register();
Chris@0: $class_loader = $apc_loader;
Chris@0: }
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * Authorized file system operations:
Chris@0: *
Chris@0: * The Update Manager module included with Drupal provides a mechanism for
Chris@0: * site administrators to securely install missing updates for the site
Chris@0: * directly through the web user interface. On securely-configured servers,
Chris@0: * the Update manager will require the administrator to provide SSH or FTP
Chris@0: * credentials before allowing the installation to proceed; this allows the
Chris@0: * site to update the new files as the user who owns all the Drupal files,
Chris@0: * instead of as the user the webserver is running as. On servers where the
Chris@0: * webserver user is itself the owner of the Drupal files, the administrator
Chris@0: * will not be prompted for SSH or FTP credentials (note that these server
Chris@0: * setups are common on shared hosting, but are inherently insecure).
Chris@0: *
Chris@0: * Some sites might wish to disable the above functionality, and only update
Chris@0: * the code directly via SSH or FTP themselves. This setting completely
Chris@0: * disables all functionality related to these authorized file operations.
Chris@0: *
Chris@0: * @see https://www.drupal.org/node/244924
Chris@0: *
Chris@0: * Remove the leading hash signs to disable.
Chris@0: */
Chris@0: # $settings['allow_authorize_operations'] = FALSE;
Chris@0:
Chris@0: /**
Chris@0: * Default mode for directories and files written by Drupal.
Chris@0: *
Chris@0: * Value should be in PHP Octal Notation, with leading zero.
Chris@0: */
Chris@0: # $settings['file_chmod_directory'] = 0775;
Chris@0: # $settings['file_chmod_file'] = 0664;
Chris@0:
Chris@0: /**
Chris@0: * Public file base URL:
Chris@0: *
Chris@0: * An alternative base URL to be used for serving public files. This must
Chris@0: * include any leading directory path.
Chris@0: *
Chris@0: * A different value from the domain used by Drupal to be used for accessing
Chris@0: * public files. This can be used for a simple CDN integration, or to improve
Chris@0: * security by serving user-uploaded files from a different domain or subdomain
Chris@0: * pointing to the same server. Do not include a trailing slash.
Chris@0: */
Chris@0: # $settings['file_public_base_url'] = 'http://downloads.example.com/files';
Chris@0:
Chris@0: /**
Chris@0: * Public file path:
Chris@0: *
Chris@0: * A local file system path where public files will be stored. This directory
Chris@0: * must exist and be writable by Drupal. This directory must be relative to
Chris@0: * the Drupal installation directory and be accessible over the web.
Chris@0: */
Chris@0: # $settings['file_public_path'] = 'sites/default/files';
Chris@0:
Chris@0: /**
Chris@0: * Private file path:
Chris@0: *
Chris@0: * A local file system path where private files will be stored. This directory
Chris@0: * must be absolute, outside of the Drupal installation directory and not
Chris@0: * accessible over the web.
Chris@0: *
Chris@0: * Note: Caches need to be cleared when this value is changed to make the
Chris@0: * private:// stream wrapper available to the system.
Chris@0: *
Chris@0: * See https://www.drupal.org/documentation/modules/file for more information
Chris@0: * about securing private files.
Chris@0: */
Chris@0: # $settings['file_private_path'] = '';
Chris@0:
Chris@0: /**
Chris@0: * Session write interval:
Chris@0: *
Chris@0: * Set the minimum interval between each session write to database.
Chris@0: * For performance reasons it defaults to 180.
Chris@0: */
Chris@0: # $settings['session_write_interval'] = 180;
Chris@0:
Chris@0: /**
Chris@0: * String overrides:
Chris@0: *
Chris@0: * To override specific strings on your site with or without enabling the Locale
Chris@0: * module, add an entry to this list. This functionality allows you to change
Chris@0: * a small number of your site's default English language interface strings.
Chris@0: *
Chris@0: * Remove the leading hash signs to enable.
Chris@0: *
Chris@0: * The "en" part of the variable name, is dynamic and can be any langcode of
Chris@0: * any added language. (eg locale_custom_strings_de for german).
Chris@0: */
Chris@0: # $settings['locale_custom_strings_en'][''] = array(
Chris@0: # 'forum' => 'Discussion board',
Chris@0: # '@count min' => '@count minutes',
Chris@0: # );
Chris@0:
Chris@0: /**
Chris@0: * A custom theme for the offline page:
Chris@0: *
Chris@0: * This applies when the site is explicitly set to maintenance mode through the
Chris@0: * administration page or when the database is inactive due to an error.
Chris@0: * The template file should also be copied into the theme. It is located inside
Chris@0: * 'core/modules/system/templates/maintenance-page.html.twig'.
Chris@0: *
Chris@0: * Note: This setting does not apply to installation and update pages.
Chris@0: */
Chris@0: # $settings['maintenance_theme'] = 'bartik';
Chris@0:
Chris@0: /**
Chris@0: * PHP settings:
Chris@0: *
Chris@0: * To see what PHP settings are possible, including whether they can be set at
Chris@0: * runtime (by using ini_set()), read the PHP documentation:
Chris@0: * http://php.net/manual/ini.list.php
Chris@0: * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime
Chris@0: * settings and the .htaccess file for non-runtime settings.
Chris@0: * Settings defined there should not be duplicated here so as to avoid conflict
Chris@0: * issues.
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * If you encounter a situation where users post a large amount of text, and
Chris@0: * the result is stripped out upon viewing but can still be edited, Drupal's
Chris@0: * output filter may not have sufficient memory to process it. If you
Chris@0: * experience this issue, you may wish to uncomment the following two lines
Chris@0: * and increase the limits of these variables. For more information, see
Chris@0: * http://php.net/manual/pcre.configuration.php.
Chris@0: */
Chris@0: # ini_set('pcre.backtrack_limit', 200000);
Chris@0: # ini_set('pcre.recursion_limit', 200000);
Chris@0:
Chris@0: /**
Chris@0: * Active configuration settings.
Chris@0: *
Chris@0: * By default, the active configuration is stored in the database in the
Chris@0: * {config} table. To use a different storage mechanism for the active
Chris@0: * configuration, do the following prior to installing:
Chris@0: * - Create an "active" directory and declare its path in $config_directories
Chris@0: * as explained under the 'Location of the site configuration files' section
Chris@0: * above in this file. To enhance security, you can declare a path that is
Chris@0: * outside your document root.
Chris@0: * - Override the 'bootstrap_config_storage' setting here. It must be set to a
Chris@0: * callable that returns an object that implements
Chris@0: * \Drupal\Core\Config\StorageInterface.
Chris@0: * - Override the service definition 'config.storage.active'. Put this
Chris@0: * override in a services.yml file in the same directory as settings.php
Chris@0: * (definitions in this file will override service definition defaults).
Chris@0: */
Chris@0: # $settings['bootstrap_config_storage'] = array('Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage');
Chris@0:
Chris@0: /**
Chris@0: * Configuration overrides.
Chris@0: *
Chris@0: * To globally override specific configuration values for this site,
Chris@0: * set them here. You usually don't need to use this feature. This is
Chris@0: * useful in a configuration file for a vhost or directory, rather than
Chris@0: * the default settings.php.
Chris@0: *
Chris@0: * Note that any values you provide in these variable overrides will not be
Chris@0: * viewable from the Drupal administration interface. The administration
Chris@0: * interface displays the values stored in configuration so that you can stage
Chris@0: * changes to other environments that don't have the overrides.
Chris@0: *
Chris@0: * There are particular configuration values that are risky to override. For
Chris@0: * example, overriding the list of installed modules in 'core.extension' is not
Chris@0: * supported as module install or uninstall has not occurred. Other examples
Chris@0: * include field storage configuration, because it has effects on database
Chris@0: * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
Chris@0: * a way that is not config override aware. Also, note that changing
Chris@0: * configuration values in settings.php will not fire any of the configuration
Chris@0: * change events.
Chris@0: */
Chris@0: # $config['system.file']['path']['temporary'] = '/tmp';
Chris@0: # $config['system.site']['name'] = 'My Drupal site';
Chris@0: # $config['system.theme']['default'] = 'stark';
Chris@0: # $config['user.settings']['anonymous'] = 'Visitor';
Chris@0:
Chris@0: /**
Chris@0: * Fast 404 pages:
Chris@0: *
Chris@0: * Drupal can generate fully themed 404 pages. However, some of these responses
Chris@0: * are for images or other resource files that are not displayed to the user.
Chris@0: * This can waste bandwidth, and also generate server load.
Chris@0: *
Chris@0: * The options below return a simple, fast 404 page for URLs matching a
Chris@0: * specific pattern:
Chris@0: * - $config['system.performance']['fast_404']['exclude_paths']: A regular
Chris@0: * expression to match paths to exclude, such as images generated by image
Chris@0: * styles, or dynamically-resized images. The default pattern provided below
Chris@0: * also excludes the private file system. If you need to add more paths, you
Chris@0: * can add '|path' to the expression.
Chris@0: * - $config['system.performance']['fast_404']['paths']: A regular expression to
Chris@0: * match paths that should return a simple 404 page, rather than the fully
Chris@0: * themed 404 page. If you don't have any aliases ending in htm or html you
Chris@0: * can add '|s?html?' to the expression.
Chris@0: * - $config['system.performance']['fast_404']['html']: The html to return for
Chris@0: * simple 404 pages.
Chris@0: *
Chris@0: * Remove the leading hash signs if you would like to alter this functionality.
Chris@0: */
Chris@0: # $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
Chris@0: # $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
Chris@0: # $config['system.performance']['fast_404']['html'] = '404 Not FoundNot Found
The requested URL "@path" was not found on this server.
';
Chris@0:
Chris@0: /**
Chris@0: * Load services definition file.
Chris@0: */
Chris@0: $settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
Chris@0:
Chris@0: /**
Chris@0: * Override the default service container class.
Chris@0: *
Chris@0: * This is useful for example to trace the service container for performance
Chris@0: * tracking purposes, for testing a service container with an error condition or
Chris@0: * to test a service container that throws an exception.
Chris@0: */
Chris@0: # $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
Chris@0:
Chris@0: /**
Chris@0: * Override the default yaml parser class.
Chris@0: *
Chris@0: * Provide a fully qualified class name here if you would like to provide an
Chris@0: * alternate implementation YAML parser. The class must implement the
Chris@0: * \Drupal\Component\Serialization\SerializationInterface interface.
Chris@0: */
Chris@0: # $settings['yaml_parser_class'] = NULL;
Chris@0:
Chris@0: /**
Chris@0: * Trusted host configuration.
Chris@0: *
Chris@0: * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
Chris@0: * header spoofing.
Chris@0: *
Chris@0: * To enable the trusted host mechanism, you enable your allowable hosts
Chris@0: * in $settings['trusted_host_patterns']. This should be an array of regular
Chris@0: * expression patterns, without delimiters, representing the hosts you would
Chris@0: * like to allow.
Chris@0: *
Chris@0: * For example:
Chris@0: * @code
Chris@0: * $settings['trusted_host_patterns'] = array(
Chris@0: * '^www\.example\.com$',
Chris@0: * );
Chris@0: * @endcode
Chris@0: * will allow the site to only run from www.example.com.
Chris@0: *
Chris@0: * If you are running multisite, or if you are running your site from
Chris@0: * different domain names (eg, you don't redirect http://www.example.com to
Chris@0: * http://example.com), you should specify all of the host patterns that are
Chris@0: * allowed by your site.
Chris@0: *
Chris@0: * For example:
Chris@0: * @code
Chris@0: * $settings['trusted_host_patterns'] = array(
Chris@0: * '^example\.com$',
Chris@0: * '^.+\.example\.com$',
Chris@0: * '^example\.org$',
Chris@0: * '^.+\.example\.org$',
Chris@0: * );
Chris@0: * @endcode
Chris@0: * will allow the site to run off of all variants of example.com and
Chris@0: * example.org, with all subdomains included.
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * The default list of directories that will be ignored by Drupal's file API.
Chris@0: *
Chris@0: * By default ignore node_modules and bower_components folders to avoid issues
Chris@0: * with common frontend tools and recursive scanning of directories looking for
Chris@0: * extensions.
Chris@0: *
Chris@0: * @see file_scan_directory()
Chris@0: * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory()
Chris@0: */
Chris@0: $settings['file_scan_ignore_directories'] = [
Chris@0: 'node_modules',
Chris@0: 'bower_components',
Chris@0: ];
Chris@0:
Chris@0: /**
Chris@0: * The default number of entities to update in a batch process.
Chris@0: *
Chris@0: * This is used by update and post-update functions that need to go through and
Chris@0: * change all the entities on a site, so it is useful to increase this number
Chris@0: * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a
Chris@0: * larger number of entities to be processed in a single batch run.
Chris@0: */
Chris@0: $settings['entity_update_batch_size'] = 50;
Chris@0:
Chris@0: /**
Chris@0: * Load local development override configuration, if available.
Chris@0: *
Chris@0: * Use settings.local.php to override variables on secondary (staging,
Chris@0: * development, etc) installations of this site. Typically used to disable
Chris@0: * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
Chris@0: * other things that should not happen on development and testing sites.
Chris@0: *
Chris@0: * Keep this code block at the end of this file to take full effect.
Chris@0: */
Chris@0: #
Chris@0: # if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
Chris@0: # include $app_root . '/' . $site_path . '/settings.local.php';
Chris@0: # }