Chris@0: 'mysql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'username',
Chris@0: * 'password' => 'password',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'port' => 3306,
Chris@0: * 'prefix' => 'myprefix_',
Chris@0: * 'collation' => 'utf8_general_ci',
Chris@0: * );
Chris@0: * @endcode
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 master/slave replication, as Drupal may try to connect
Chris@0: * to a slave server when appropriate and if one is not available will simply
Chris@0: * fall back to the single master server.
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']['slave'][] = $info_array;
Chris@0: * $databases['default']['slave'][] = $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 master database
Chris@0: * (the second level default). The second and third lines create an array
Chris@0: * of potential slave 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: * For a single database configuration, the following is sufficient:
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'mysql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'username',
Chris@0: * 'password' => 'password',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'prefix' => 'main_',
Chris@0: * 'collation' => 'utf8_general_ci',
Chris@0: * );
Chris@0: * @endcode
Chris@0: *
Chris@0: * For handling full UTF-8 in MySQL, including multi-byte characters such as
Chris@0: * emojis, Asian symbols, and mathematical symbols, you may set the collation
Chris@0: * and charset to "utf8mb4" prior to running install.php:
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'mysql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'username',
Chris@0: * 'password' => 'password',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'charset' => 'utf8mb4',
Chris@0: * 'collation' => 'utf8mb4_general_ci',
Chris@0: * );
Chris@0: * @endcode
Chris@0: * When using this setting on an existing installation, ensure that all existing
Chris@0: * tables have been converted to the utf8mb4 charset, for example by using the
Chris@0: * utf8mb4_convert contributed project available at
Chris@0: * https://www.drupal.org/project/utf8mb4_convert, so as to prevent mixing data
Chris@0: * with different charsets.
Chris@0: * Note this should only be used when all of the following conditions are met:
Chris@0: * - In order to allow for large indexes, MySQL must be set up with the
Chris@0: * following my.cnf settings:
Chris@0: * [mysqld]
Chris@0: * innodb_large_prefix=true
Chris@0: * innodb_file_format=barracuda
Chris@0: * innodb_file_per_table=true
Chris@0: * These settings are available as of MySQL 5.5.14, and are defaults in
Chris@0: * MySQL 5.7.7 and up.
Chris@0: * - The PHP MySQL driver must support the utf8mb4 charset (libmysqlclient
Chris@0: * 5.5.3 and up, as well as mysqlnd 5.0.9 and up).
Chris@0: * - The MySQL server must support the utf8mb4 charset (5.5.3 and up).
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: * 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: *
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: These defaults are designed for database portability. Changing them
Chris@0: * may cause unexpected behavior, including potential data loss.
Chris@0: *
Chris@0: * @see DatabaseConnection_mysql::__construct
Chris@0: * @see DatabaseConnection_pgsql::__construct
Chris@0: * @see DatabaseConnection_sqlite::__construct
Chris@0: *
Chris@0: * Database configuration format:
Chris@0: * @code
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'mysql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'username',
Chris@0: * 'password' => 'password',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'prefix' => '',
Chris@0: * );
Chris@0: * $databases['default']['default'] = array(
Chris@0: * 'driver' => 'pgsql',
Chris@0: * 'database' => 'databasename',
Chris@0: * 'username' => 'username',
Chris@0: * 'password' => 'password',
Chris@0: * 'host' => 'localhost',
Chris@0: * 'prefix' => '',
Chris@0: * );
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: $databases = array (
Chris@0: 'default' =>
Chris@0: array (
Chris@0: 'default' =>
Chris@0: array (
Chris@0: 'database' => '{{ db_name }}',
Chris@0: 'username' => '{{ db_user }}',
Chris@0: 'password' => '{{ db_password }}',
Chris@0: 'host' => 'localhost',
Chris@0: 'port' => '',
Chris@0: 'driver' => '{{ db_driver }}',
Chris@0: 'prefix' => '',
Chris@0: ),
Chris@0: ),
Chris@0: );
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: $update_free_access = FALSE;
Chris@0:
Chris@0: /**
Chris@0: * Salt for one-time login links and 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. If this variable is empty, a hash
Chris@0: * of the serialized database credentials will be used as a fallback salt.
Chris@0: *
Chris@0: * For enhanced security, you may set this variable to a value using the
Chris@0: * contents of a file outside your docroot that is never saved together
Chris@0: * with any backups of your Drupal files and database.
Chris@0: *
Chris@0: * Example:
Chris@0: * $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
Chris@0: *
Chris@0: */
Chris@0: $drupal_hash_salt = '{{ hash_salt }}';
Chris@0:
Chris@0: /**
Chris@0: * Base URL (optional).
Chris@0: *
Chris@0: * If Drupal is generating incorrect URLs on your site, which could
Chris@0: * be in HTML headers (links to CSS and JS files) or visible links on pages
Chris@0: * (such as in menus), uncomment the Base URL statement below (remove the
Chris@0: * leading hash sign) and fill in the absolute URL to your Drupal installation.
Chris@0: *
Chris@0: * You might also want to force users to use a given domain.
Chris@0: * See the .htaccess file for more information.
Chris@0: *
Chris@0: * Examples:
Chris@0: * $base_url = 'http://www.example.com';
Chris@0: * $base_url = 'http://www.example.com:8888';
Chris@0: * $base_url = 'http://www.example.com/drupal';
Chris@0: * $base_url = 'https://www.example.com:8888/drupal';
Chris@0: *
Chris@0: * It is not allowed to have a trailing slash; Drupal will add it
Chris@0: * for you.
Chris@0: */
Chris@0: # $base_url = 'http://www.example.com'; // NO trailing slash!
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://www.php.net/manual/ini.list.php
Chris@0: * See drupal_environment_initialize() in includes/bootstrap.inc for required
Chris@0: * runtime settings and the .htaccess file for non-runtime settings. Settings
Chris@0: * defined there should not be duplicated here so as to avoid conflict issues.
Chris@0: */
Chris@0:
Chris@0: /**
Chris@0: * Some distributions of Linux (most notably Debian) ship their PHP
Chris@0: * installations with garbage collection (gc) disabled. Since Drupal depends on
Chris@0: * PHP's garbage collection for clearing sessions, ensure that garbage
Chris@0: * collection occurs by using the most common settings.
Chris@0: */
Chris@0: ini_set('session.gc_probability', 1);
Chris@0: ini_set('session.gc_divisor', 100);
Chris@0:
Chris@0: /**
Chris@0: * Set session lifetime (in seconds), i.e. the time from the user's last visit
Chris@0: * to the active session may be deleted by the session garbage collector. When
Chris@0: * a session is deleted, authenticated users are logged out, and the contents
Chris@0: * of the user's $_SESSION variable is discarded.
Chris@0: */
Chris@0: ini_set('session.gc_maxlifetime', 200000);
Chris@0:
Chris@0: /**
Chris@0: * Set session cookie lifetime (in seconds), i.e. the time from the session is
Chris@0: * created to the cookie expires, i.e. when the browser is expected to discard
Chris@0: * the cookie. The value 0 means "until the browser is closed".
Chris@0: */
Chris@0: ini_set('session.cookie_lifetime', 2000000);
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: * Drupal automatically generates a unique session cookie name for each site
Chris@0: * based on its full domain name. If you have multiple domains pointing at the
Chris@0: * same Drupal site, you can either redirect them all to a single domain (see
Chris@0: * comment in .htaccess), or uncomment the line below and specify their shared
Chris@0: * base domain. Doing so assures that users remain logged in as they cross
Chris@0: * between your various domains. Make sure to always start the $cookie_domain
Chris@0: * with a leading dot, as per RFC 2109.
Chris@0: */
Chris@0: # $cookie_domain = '.example.com';
Chris@0:
Chris@0: /**
Chris@0: * Variable overrides:
Chris@0: *
Chris@0: * To override specific entries in the 'variable' table 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. Any configuration setting from the 'variable'
Chris@0: * table can be given a new value. Note that any values you provide in
Chris@0: * these variable overrides will not be modifiable from the Drupal
Chris@0: * administration interface.
Chris@0: *
Chris@0: * The following overrides are examples:
Chris@0: * - site_name: Defines the site's name.
Chris@0: * - theme_default: Defines the default theme for this site.
Chris@0: * - anonymous: Defines the human-readable name of anonymous users.
Chris@0: * Remove the leading hash signs to enable.
Chris@0: */
Chris@0: # $conf['site_name'] = 'My Drupal site';
Chris@0: # $conf['theme_default'] = 'garland';
Chris@0: # $conf['anonymous'] = 'Visitor';
Chris@0:
Chris@0: /**
Chris@0: * A custom theme can be set for the offline page. This applies when the site
Chris@0: * is explicitly set to maintenance mode through the administration page or when
Chris@0: * the database is inactive due to an error. It can be set through the
Chris@0: * 'maintenance_theme' key. The template file should also be copied into the
Chris@0: * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
Chris@0: * Note: This setting does not apply to installation and update pages.
Chris@0: */
Chris@0: # $conf['maintenance_theme'] = 'bartik';
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 $conf['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 $conf['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 $conf['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: # $conf['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 $conf['reverse_proxy'] is TRUE.
Chris@0: */
Chris@0: # $conf['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: # $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
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: # $conf['omit_vary_cookie'] = TRUE;
Chris@0:
Chris@0: /**
Chris@0: * CSS/JS aggregated file gzip compression:
Chris@0: *
Chris@0: * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
Chris@0: * store a gzip compressed (.gz) copy of the aggregated files. If this file is
Chris@0: * available then rewrite rules in the default .htaccess file will serve these
Chris@0: * files to browsers that accept gzip encoded content. This allows pages to load
Chris@0: * faster for these users and has minimal impact on server load. If you are
Chris@0: * using a webserver other than Apache httpd, or a caching reverse proxy that is
Chris@0: * configured to cache and compress these files itself you may want to uncomment
Chris@0: * one or both of the below lines, which will prevent gzip files being stored.
Chris@0: */
Chris@0: # $conf['css_gzip_compression'] = FALSE;
Chris@0: # $conf['js_gzip_compression'] = FALSE;
Chris@0:
Chris@0: /**
Chris@0: * Block caching:
Chris@0: *
Chris@0: * Block caching may not be compatible with node access modules depending on
Chris@0: * how the original block cache policy is defined by the module that provides
Chris@0: * the block. By default, Drupal therefore disables block caching when one or
Chris@0: * more modules implement hook_node_grants(). If you consider block caching to
Chris@0: * be safe on your site and want to bypass this restriction, uncomment the line
Chris@0: * below.
Chris@0: */
Chris@0: # $conf['block_cache_bypass_node_grants'] = TRUE;
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: # $conf['locale_custom_strings_en'][''] = array(
Chris@0: # 'forum' => 'Discussion board',
Chris@0: # '@count min' => '@count minutes',
Chris@0: # );
Chris@0:
Chris@0: /**
Chris@0: *
Chris@0: * IP blocking:
Chris@0: *
Chris@0: * To bypass database queries for denied IP addresses, use this setting.
Chris@0: * Drupal queries the {blocked_ips} table by default on every page request
Chris@0: * for both authenticated and anonymous users. This allows the system to
Chris@0: * block IP addresses from within the administrative interface and before any
Chris@0: * modules are loaded. However on high traffic websites you may want to avoid
Chris@0: * this query, allowing you to bypass database access altogether for anonymous
Chris@0: * users under certain caching configurations.
Chris@0: *
Chris@0: * If using this setting, you will need to add back any IP addresses which
Chris@0: * you may have blocked via the administrative interface. Each element of this
Chris@0: * array represents a blocked IP address. Uncommenting the array and leaving it
Chris@0: * empty will have the effect of disabling IP blocking on your site.
Chris@0: *
Chris@0: * Remove the leading hash signs to enable.
Chris@0: */
Chris@0: # $conf['blocked_ips'] = array(
Chris@0: # 'a.b.c.d',
Chris@0: # );
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: * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
Chris@0: * such as images generated by image styles, or dynamically-resized images.
Chris@0: * The default pattern provided below also excludes the private file system.
Chris@0: * If you need to add more paths, you can add '|path' to the expression.
Chris@0: * - 404_fast_paths: A regular expression to match paths that should return a
Chris@0: * simple 404 page, rather than the fully themed 404 page. If you don't have
Chris@0: * any aliases ending in htm or html you can add '|s?html?' to the expression.
Chris@0: * - 404_fast_html: The html to return for simple 404 pages.
Chris@0: *
Chris@0: * Add leading hash signs if you would like to disable this functionality.
Chris@0: */
Chris@0: $conf['404_fast_paths_exclude'] = '/\/(?:styles)|(?:system\/files)\//';
Chris@0: $conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
Chris@0: $conf['404_fast_html'] = '404 Not FoundNot Found
The requested URL "@path" was not found on this server.
';
Chris@0:
Chris@0: /**
Chris@0: * By default the page request process will return a fast 404 page for missing
Chris@0: * files if they match the regular expression set in '404_fast_paths' and not
Chris@0: * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
Chris@0: * the Drupal system log.
Chris@0: *
Chris@0: * You can choose to return a fast 404 page earlier for missing pages (as soon
Chris@0: * as settings.php is loaded) by uncommenting the line below. This speeds up
Chris@0: * server response time when loading 404 error pages and prevents the 404 error
Chris@0: * from being logged in the Drupal system log. In order to prevent valid pages
Chris@0: * such as image styles and other generated content that may match the
Chris@0: * '404_fast_paths' regular expression from returning 404 errors, it is
Chris@0: * necessary to add them to the '404_fast_paths_exclude' regular expression
Chris@0: * above. Make sure that you understand the effects of this feature before
Chris@0: * uncommenting the line below.
Chris@0: */
Chris@0: # drupal_fast_404();
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
Chris@0: * the proxy settings here. Currently only basic authentication is supported
Chris@0: * by using the username and password variables. The proxy_user_agent variable
Chris@0: * can be set to NULL for proxies that require no User-Agent header or to a
Chris@0: * non-empty string for proxies that limit requests to a specific agent. The
Chris@0: * proxy_exceptions variable is an array of host names to be accessed directly,
Chris@0: * not via proxy.
Chris@0: */
Chris@0: # $conf['proxy_server'] = '';
Chris@0: # $conf['proxy_port'] = 8080;
Chris@0: # $conf['proxy_username'] = '';
Chris@0: # $conf['proxy_password'] = '';
Chris@0: # $conf['proxy_user_agent'] = '';
Chris@0: # $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
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 http://drupal.org/node/244924
Chris@0: *
Chris@0: * Remove the leading hash signs to disable.
Chris@0: */
Chris@0: # $conf['allow_authorize_operations'] = FALSE;
Chris@0:
Chris@0: /**
Chris@0: * Theme debugging:
Chris@0: *
Chris@0: * When debugging is enabled:
Chris@0: * - The markup of each template is surrounded by HTML comments that contain
Chris@0: * theming information, such as template file name suggestions.
Chris@0: * - Note that this debugging markup will cause automated tests that directly
Chris@0: * check rendered HTML to fail.
Chris@0: *
Chris@0: * For more information about debugging theme templates, see
Chris@0: * https://www.drupal.org/node/223440#theme-debug.
Chris@0: *
Chris@0: * Not recommended in production environments.
Chris@0: *
Chris@0: * Remove the leading hash sign to enable.
Chris@0: */
Chris@0: # $conf['theme_debug'] = TRUE;
Chris@0:
Chris@0: /**
Chris@0: * CSS identifier double underscores allowance:
Chris@0: *
Chris@0: * To allow CSS identifiers to contain double underscores (.example__selector)
Chris@0: * for Drupal's BEM-style naming standards, uncomment the line below.
Chris@0: * Note that if you change this value in existing sites, existing page styles
Chris@0: * may be broken.
Chris@0: *
Chris@0: * @see drupal_clean_css_identifier()
Chris@0: */
Chris@0: # $conf['allow_css_double_underscores'] = TRUE;