1. 7 sites/default/default.settings.php
  2. 6 sites/default/default.settings.php
  3. 8 sites/default/default.settings.php

Drupal site-specific configuration file.

IMPORTANT NOTE: This file may have been set to read-only by the Drupal installation program. If you make changes to this file, be sure to protect it again after making your modifications. Failure to remove write permissions to this file is a security risk.

The configuration file to be loaded is based upon the rules below. However if the multisite aliasing file named sites/sites.php is present, it will be loaded, and the aliases in the array $sites will override the default directory rules below. See sites/example.sites.php for more information about aliases.

The configuration directory will be discovered by stripping the website's hostname from left to right and pathname from right to left. The first configuration file found will be used and any others will be ignored. If no other configuration file is found then the default configuration file at 'sites/default' will be used.

For example, for a fictitious site installed at http://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched for in the following directories:

  • sites/default

Note that if you are installing on a non-standard port number, prefix the hostname with that number. For example, http://www.drupal.org:8080/mysite/test/ could be loaded from sites/8080.www.drupal.org.mysite.test/.

See also

example.sites.php

conf_path()

File

sites/default/default.settings.php
View source
  1. <?php
  2. /**
  3. * @file
  4. * Drupal site-specific configuration file.
  5. *
  6. * IMPORTANT NOTE:
  7. * This file may have been set to read-only by the Drupal installation program.
  8. * If you make changes to this file, be sure to protect it again after making
  9. * your modifications. Failure to remove write permissions to this file is a
  10. * security risk.
  11. *
  12. * The configuration file to be loaded is based upon the rules below. However
  13. * if the multisite aliasing file named sites/sites.php is present, it will be
  14. * loaded, and the aliases in the array $sites will override the default
  15. * directory rules below. See sites/example.sites.php for more information about
  16. * aliases.
  17. *
  18. * The configuration directory will be discovered by stripping the website's
  19. * hostname from left to right and pathname from right to left. The first
  20. * configuration file found will be used and any others will be ignored. If no
  21. * other configuration file is found then the default configuration file at
  22. * 'sites/default' will be used.
  23. *
  24. * For example, for a fictitious site installed at
  25. * http://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
  26. * for in the following directories:
  27. *
  28. * - sites/8080.www.drupal.org.mysite.test
  29. * - sites/www.drupal.org.mysite.test
  30. * - sites/drupal.org.mysite.test
  31. * - sites/org.mysite.test
  32. *
  33. * - sites/8080.www.drupal.org.mysite
  34. * - sites/www.drupal.org.mysite
  35. * - sites/drupal.org.mysite
  36. * - sites/org.mysite
  37. *
  38. * - sites/8080.www.drupal.org
  39. * - sites/www.drupal.org
  40. * - sites/drupal.org
  41. * - sites/org
  42. *
  43. * - sites/default
  44. *
  45. * Note that if you are installing on a non-standard port number, prefix the
  46. * hostname with that number. For example,
  47. * http://www.drupal.org:8080/mysite/test/ could be loaded from
  48. * sites/8080.www.drupal.org.mysite.test/.
  49. *
  50. * @see example.sites.php
  51. * @see conf_path()
  52. */
  53. /**
  54. * Database settings:
  55. *
  56. * The $databases array specifies the database connection or
  57. * connections that Drupal may use. Drupal is able to connect
  58. * to multiple databases, including multiple types of databases,
  59. * during the same request.
  60. *
  61. * Each database connection is specified as an array of settings,
  62. * similar to the following:
  63. * @code
  64. * array(
  65. * 'driver' => 'mysql',
  66. * 'database' => 'databasename',
  67. * 'username' => 'username',
  68. * 'password' => 'password',
  69. * 'host' => 'localhost',
  70. * 'port' => 3306,
  71. * 'prefix' => 'myprefix_',
  72. * 'collation' => 'utf8_general_ci',
  73. * );
  74. * @endcode
  75. *
  76. * The "driver" property indicates what Drupal database driver the
  77. * connection should use. This is usually the same as the name of the
  78. * database type, such as mysql or sqlite, but not always. The other
  79. * properties will vary depending on the driver. For SQLite, you must
  80. * specify a database file name in a directory that is writable by the
  81. * webserver. For most other drivers, you must specify a
  82. * username, password, host, and database name.
  83. *
  84. * Transaction support is enabled by default for all drivers that support it,
  85. * including MySQL. To explicitly disable it, set the 'transactions' key to
  86. * FALSE.
  87. * Note that some configurations of MySQL, such as the MyISAM engine, don't
  88. * support it and will proceed silently even if enabled. If you experience
  89. * transaction related crashes with such configuration, set the 'transactions'
  90. * key to FALSE.
  91. *
  92. * For each database, you may optionally specify multiple "target" databases.
  93. * A target database allows Drupal to try to send certain queries to a
  94. * different database if it can but fall back to the default connection if not.
  95. * That is useful for master/slave replication, as Drupal may try to connect
  96. * to a slave server when appropriate and if one is not available will simply
  97. * fall back to the single master server.
  98. *
  99. * The general format for the $databases array is as follows:
  100. * @code
  101. * $databases['default']['default'] = $info_array;
  102. * $databases['default']['slave'][] = $info_array;
  103. * $databases['default']['slave'][] = $info_array;
  104. * $databases['extra']['default'] = $info_array;
  105. * @endcode
  106. *
  107. * In the above example, $info_array is an array of settings described above.
  108. * The first line sets a "default" database that has one master database
  109. * (the second level default). The second and third lines create an array
  110. * of potential slave databases. Drupal will select one at random for a given
  111. * request as needed. The fourth line creates a new database with a name of
  112. * "extra".
  113. *
  114. * For a single database configuration, the following is sufficient:
  115. * @code
  116. * $databases['default']['default'] = array(
  117. * 'driver' => 'mysql',
  118. * 'database' => 'databasename',
  119. * 'username' => 'username',
  120. * 'password' => 'password',
  121. * 'host' => 'localhost',
  122. * 'prefix' => 'main_',
  123. * 'collation' => 'utf8_general_ci',
  124. * );
  125. * @endcode
  126. *
  127. * You can optionally set prefixes for some or all database table names
  128. * by using the 'prefix' setting. If a prefix is specified, the table
  129. * name will be prepended with its value. Be sure to use valid database
  130. * characters only, usually alphanumeric and underscore. If no prefixes
  131. * are desired, leave it as an empty string ''.
  132. *
  133. * To have all database names prefixed, set 'prefix' as a string:
  134. * @code
  135. * 'prefix' => 'main_',
  136. * @endcode
  137. * To provide prefixes for specific tables, set 'prefix' as an array.
  138. * The array's keys are the table names and the values are the prefixes.
  139. * The 'default' element is mandatory and holds the prefix for any tables
  140. * not specified elsewhere in the array. Example:
  141. * @code
  142. * 'prefix' => array(
  143. * 'default' => 'main_',
  144. * 'users' => 'shared_',
  145. * 'sessions' => 'shared_',
  146. * 'role' => 'shared_',
  147. * 'authmap' => 'shared_',
  148. * ),
  149. * @endcode
  150. * You can also use a reference to a schema/database as a prefix. This may be
  151. * useful if your Drupal installation exists in a schema that is not the default
  152. * or you want to access several databases from the same code base at the same
  153. * time.
  154. * Example:
  155. * @code
  156. * 'prefix' => array(
  157. * 'default' => 'main.',
  158. * 'users' => 'shared.',
  159. * 'sessions' => 'shared.',
  160. * 'role' => 'shared.',
  161. * 'authmap' => 'shared.',
  162. * );
  163. * @endcode
  164. * NOTE: MySQL and SQLite's definition of a schema is a database.
  165. *
  166. * Advanced users can add or override initial commands to execute when
  167. * connecting to the database server, as well as PDO connection settings. For
  168. * example, to enable MySQL SELECT queries to exceed the max_join_size system
  169. * variable, and to reduce the database connection timeout to 5 seconds:
  170. *
  171. * @code
  172. * $databases['default']['default'] = array(
  173. * 'init_commands' => array(
  174. * 'big_selects' => 'SET SQL_BIG_SELECTS=1',
  175. * ),
  176. * 'pdo' => array(
  177. * PDO::ATTR_TIMEOUT => 5,
  178. * ),
  179. * );
  180. * @endcode
  181. *
  182. * WARNING: These defaults are designed for database portability. Changing them
  183. * may cause unexpected behavior, including potential data loss.
  184. *
  185. * @see DatabaseConnection_mysql::__construct
  186. * @see DatabaseConnection_pgsql::__construct
  187. * @see DatabaseConnection_sqlite::__construct
  188. *
  189. * Database configuration format:
  190. * @code
  191. * $databases['default']['default'] = array(
  192. * 'driver' => 'mysql',
  193. * 'database' => 'databasename',
  194. * 'username' => 'username',
  195. * 'password' => 'password',
  196. * 'host' => 'localhost',
  197. * 'prefix' => '',
  198. * );
  199. * $databases['default']['default'] = array(
  200. * 'driver' => 'pgsql',
  201. * 'database' => 'databasename',
  202. * 'username' => 'username',
  203. * 'password' => 'password',
  204. * 'host' => 'localhost',
  205. * 'prefix' => '',
  206. * );
  207. * $databases['default']['default'] = array(
  208. * 'driver' => 'sqlite',
  209. * 'database' => '/path/to/databasefilename',
  210. * );
  211. * @endcode
  212. */
  213. $databases = array();
  214. /**
  215. * Access control for update.php script.
  216. *
  217. * If you are updating your Drupal installation using the update.php script but
  218. * are not logged in using either an account with the "Administer software
  219. * updates" permission or the site maintenance account (the account that was
  220. * created during installation), you will need to modify the access check
  221. * statement below. Change the FALSE to a TRUE to disable the access check.
  222. * After finishing the upgrade, be sure to open this file again and change the
  223. * TRUE back to a FALSE!
  224. */
  225. $update_free_access = FALSE;
  226. /**
  227. * Salt for one-time login links and cancel links, form tokens, etc.
  228. *
  229. * This variable will be set to a random value by the installer. All one-time
  230. * login links will be invalidated if the value is changed. Note that if your
  231. * site is deployed on a cluster of web servers, you must ensure that this
  232. * variable has the same value on each server. If this variable is empty, a hash
  233. * of the serialized database credentials will be used as a fallback salt.
  234. *
  235. * For enhanced security, you may set this variable to a value using the
  236. * contents of a file outside your docroot that is never saved together
  237. * with any backups of your Drupal files and database.
  238. *
  239. * Example:
  240. * $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
  241. *
  242. */
  243. $drupal_hash_salt = '';
  244. /**
  245. * Base URL (optional).
  246. *
  247. * If Drupal is generating incorrect URLs on your site, which could
  248. * be in HTML headers (links to CSS and JS files) or visible links on pages
  249. * (such as in menus), uncomment the Base URL statement below (remove the
  250. * leading hash sign) and fill in the absolute URL to your Drupal installation.
  251. *
  252. * You might also want to force users to use a given domain.
  253. * See the .htaccess file for more information.
  254. *
  255. * Examples:
  256. * $base_url = 'http://www.example.com';
  257. * $base_url = 'http://www.example.com:8888';
  258. * $base_url = 'http://www.example.com/drupal';
  259. * $base_url = 'https://www.example.com:8888/drupal';
  260. *
  261. * It is not allowed to have a trailing slash; Drupal will add it
  262. * for you.
  263. */
  264. # $base_url = 'http://www.example.com'; // NO trailing slash!
  265. /**
  266. * PHP settings:
  267. *
  268. * To see what PHP settings are possible, including whether they can be set at
  269. * runtime (by using ini_set()), read the PHP documentation:
  270. * http://www.php.net/manual/ini.list.php
  271. * See drupal_environment_initialize() in includes/bootstrap.inc for required
  272. * runtime settings and the .htaccess file for non-runtime settings. Settings
  273. * defined there should not be duplicated here so as to avoid conflict issues.
  274. */
  275. /**
  276. * Some distributions of Linux (most notably Debian) ship their PHP
  277. * installations with garbage collection (gc) disabled. Since Drupal depends on
  278. * PHP's garbage collection for clearing sessions, ensure that garbage
  279. * collection occurs by using the most common settings.
  280. */
  281. ini_set('session.gc_probability', 1);
  282. ini_set('session.gc_divisor', 100);
  283. /**
  284. * Set session lifetime (in seconds), i.e. the time from the user's last visit
  285. * to the active session may be deleted by the session garbage collector. When
  286. * a session is deleted, authenticated users are logged out, and the contents
  287. * of the user's $_SESSION variable is discarded.
  288. */
  289. ini_set('session.gc_maxlifetime', 200000);
  290. /**
  291. * Set session cookie lifetime (in seconds), i.e. the time from the session is
  292. * created to the cookie expires, i.e. when the browser is expected to discard
  293. * the cookie. The value 0 means "until the browser is closed".
  294. */
  295. ini_set('session.cookie_lifetime', 2000000);
  296. /**
  297. * If you encounter a situation where users post a large amount of text, and
  298. * the result is stripped out upon viewing but can still be edited, Drupal's
  299. * output filter may not have sufficient memory to process it. If you
  300. * experience this issue, you may wish to uncomment the following two lines
  301. * and increase the limits of these variables. For more information, see
  302. * http://php.net/manual/pcre.configuration.php.
  303. */
  304. # ini_set('pcre.backtrack_limit', 200000);
  305. # ini_set('pcre.recursion_limit', 200000);
  306. /**
  307. * Drupal automatically generates a unique session cookie name for each site
  308. * based on its full domain name. If you have multiple domains pointing at the
  309. * same Drupal site, you can either redirect them all to a single domain (see
  310. * comment in .htaccess), or uncomment the line below and specify their shared
  311. * base domain. Doing so assures that users remain logged in as they cross
  312. * between your various domains. Make sure to always start the $cookie_domain
  313. * with a leading dot, as per RFC 2109.
  314. */
  315. # $cookie_domain = '.example.com';
  316. /**
  317. * Variable overrides:
  318. *
  319. * To override specific entries in the 'variable' table for this site,
  320. * set them here. You usually don't need to use this feature. This is
  321. * useful in a configuration file for a vhost or directory, rather than
  322. * the default settings.php. Any configuration setting from the 'variable'
  323. * table can be given a new value. Note that any values you provide in
  324. * these variable overrides will not be modifiable from the Drupal
  325. * administration interface.
  326. *
  327. * The following overrides are examples:
  328. * - site_name: Defines the site's name.
  329. * - theme_default: Defines the default theme for this site.
  330. * - anonymous: Defines the human-readable name of anonymous users.
  331. * Remove the leading hash signs to enable.
  332. */
  333. # $conf['site_name'] = 'My Drupal site';
  334. # $conf['theme_default'] = 'garland';
  335. # $conf['anonymous'] = 'Visitor';
  336. /**
  337. * A custom theme can be set for the offline page. This applies when the site
  338. * is explicitly set to maintenance mode through the administration page or when
  339. * the database is inactive due to an error. It can be set through the
  340. * 'maintenance_theme' key. The template file should also be copied into the
  341. * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
  342. * Note: This setting does not apply to installation and update pages.
  343. */
  344. # $conf['maintenance_theme'] = 'bartik';
  345. /**
  346. * Reverse Proxy Configuration:
  347. *
  348. * Reverse proxy servers are often used to enhance the performance
  349. * of heavily visited sites and may also provide other site caching,
  350. * security, or encryption benefits. In an environment where Drupal
  351. * is behind a reverse proxy, the real IP address of the client should
  352. * be determined such that the correct client IP address is available
  353. * to Drupal's logging, statistics, and access management systems. In
  354. * the most simple scenario, the proxy server will add an
  355. * X-Forwarded-For header to the request that contains the client IP
  356. * address. However, HTTP headers are vulnerable to spoofing, where a
  357. * malicious client could bypass restrictions by setting the
  358. * X-Forwarded-For header directly. Therefore, Drupal's proxy
  359. * configuration requires the IP addresses of all remote proxies to be
  360. * specified in $conf['reverse_proxy_addresses'] to work correctly.
  361. *
  362. * Enable this setting to get Drupal to determine the client IP from
  363. * the X-Forwarded-For header (or $conf['reverse_proxy_header'] if set).
  364. * If you are unsure about this setting, do not have a reverse proxy,
  365. * or Drupal operates in a shared hosting environment, this setting
  366. * should remain commented out.
  367. *
  368. * In order for this setting to be used you must specify every possible
  369. * reverse proxy IP address in $conf['reverse_proxy_addresses'].
  370. * If a complete list of reverse proxies is not available in your
  371. * environment (for example, if you use a CDN) you may set the
  372. * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
  373. * Be aware, however, that it is likely that this would allow IP
  374. * address spoofing unless more advanced precautions are taken.
  375. */
  376. # $conf['reverse_proxy'] = TRUE;
  377. /**
  378. * Specify every reverse proxy IP address in your environment.
  379. * This setting is required if $conf['reverse_proxy'] is TRUE.
  380. */
  381. # $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
  382. /**
  383. * Set this value if your proxy server sends the client IP in a header
  384. * other than X-Forwarded-For.
  385. */
  386. # $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
  387. /**
  388. * Page caching:
  389. *
  390. * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
  391. * views. This tells a HTTP proxy that it may return a page from its local
  392. * cache without contacting the web server, if the user sends the same Cookie
  393. * header as the user who originally requested the cached page. Without "Vary:
  394. * Cookie", authenticated users would also be served the anonymous page from
  395. * the cache. If the site has mostly anonymous users except a few known
  396. * editors/administrators, the Vary header can be omitted. This allows for
  397. * better caching in HTTP proxies (including reverse proxies), i.e. even if
  398. * clients send different cookies, they still get content served from the cache.
  399. * However, authenticated users should access the site directly (i.e. not use an
  400. * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
  401. * getting cached pages from the proxy.
  402. */
  403. # $conf['omit_vary_cookie'] = TRUE;
  404. /**
  405. * CSS/JS aggregated file gzip compression:
  406. *
  407. * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
  408. * store a gzip compressed (.gz) copy of the aggregated files. If this file is
  409. * available then rewrite rules in the default .htaccess file will serve these
  410. * files to browsers that accept gzip encoded content. This allows pages to load
  411. * faster for these users and has minimal impact on server load. If you are
  412. * using a webserver other than Apache httpd, or a caching reverse proxy that is
  413. * configured to cache and compress these files itself you may want to uncomment
  414. * one or both of the below lines, which will prevent gzip files being stored.
  415. */
  416. # $conf['css_gzip_compression'] = FALSE;
  417. # $conf['js_gzip_compression'] = FALSE;
  418. /**
  419. * Block caching:
  420. *
  421. * Block caching may not be compatible with node access modules depending on
  422. * how the original block cache policy is defined by the module that provides
  423. * the block. By default, Drupal therefore disables block caching when one or
  424. * more modules implement hook_node_grants(). If you consider block caching to
  425. * be safe on your site and want to bypass this restriction, uncomment the line
  426. * below.
  427. */
  428. # $conf['block_cache_bypass_node_grants'] = TRUE;
  429. /**
  430. * String overrides:
  431. *
  432. * To override specific strings on your site with or without enabling the Locale
  433. * module, add an entry to this list. This functionality allows you to change
  434. * a small number of your site's default English language interface strings.
  435. *
  436. * Remove the leading hash signs to enable.
  437. */
  438. # $conf['locale_custom_strings_en'][''] = array(
  439. # 'forum' => 'Discussion board',
  440. # '@count min' => '@count minutes',
  441. # );
  442. /**
  443. *
  444. * IP blocking:
  445. *
  446. * To bypass database queries for denied IP addresses, use this setting.
  447. * Drupal queries the {blocked_ips} table by default on every page request
  448. * for both authenticated and anonymous users. This allows the system to
  449. * block IP addresses from within the administrative interface and before any
  450. * modules are loaded. However on high traffic websites you may want to avoid
  451. * this query, allowing you to bypass database access altogether for anonymous
  452. * users under certain caching configurations.
  453. *
  454. * If using this setting, you will need to add back any IP addresses which
  455. * you may have blocked via the administrative interface. Each element of this
  456. * array represents a blocked IP address. Uncommenting the array and leaving it
  457. * empty will have the effect of disabling IP blocking on your site.
  458. *
  459. * Remove the leading hash signs to enable.
  460. */
  461. # $conf['blocked_ips'] = array(
  462. # 'a.b.c.d',
  463. # );
  464. /**
  465. * Fast 404 pages:
  466. *
  467. * Drupal can generate fully themed 404 pages. However, some of these responses
  468. * are for images or other resource files that are not displayed to the user.
  469. * This can waste bandwidth, and also generate server load.
  470. *
  471. * The options below return a simple, fast 404 page for URLs matching a
  472. * specific pattern:
  473. * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
  474. * such as images generated by image styles, or dynamically-resized images.
  475. * If you need to add more paths, you can add '|path' to the expression.
  476. * - 404_fast_paths: A regular expression to match paths that should return a
  477. * simple 404 page, rather than the fully themed 404 page. If you don't have
  478. * any aliases ending in htm or html you can add '|s?html?' to the expression.
  479. * - 404_fast_html: The html to return for simple 404 pages.
  480. *
  481. * Add leading hash signs if you would like to disable this functionality.
  482. */
  483. $conf['404_fast_paths_exclude'] = '/\/(?:styles)\//';
  484. $conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
  485. $conf['404_fast_html'] = '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><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>';
  486. /**
  487. * By default the page request process will return a fast 404 page for missing
  488. * files if they match the regular expression set in '404_fast_paths' and not
  489. * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
  490. * the Drupal system log.
  491. *
  492. * You can choose to return a fast 404 page earlier for missing pages (as soon
  493. * as settings.php is loaded) by uncommenting the line below. This speeds up
  494. * server response time when loading 404 error pages and prevents the 404 error
  495. * from being logged in the Drupal system log. In order to prevent valid pages
  496. * such as image styles and other generated content that may match the
  497. * '404_fast_paths' regular expression from returning 404 errors, it is
  498. * necessary to add them to the '404_fast_paths_exclude' regular expression
  499. * above. Make sure that you understand the effects of this feature before
  500. * uncommenting the line below.
  501. */
  502. # drupal_fast_404();
  503. /**
  504. * External access proxy settings:
  505. *
  506. * If your site must access the Internet via a web proxy then you can enter
  507. * the proxy settings here. Currently only basic authentication is supported
  508. * by using the username and password variables. The proxy_user_agent variable
  509. * can be set to NULL for proxies that require no User-Agent header or to a
  510. * non-empty string for proxies that limit requests to a specific agent. The
  511. * proxy_exceptions variable is an array of host names to be accessed directly,
  512. * not via proxy.
  513. */
  514. # $conf['proxy_server'] = '';
  515. # $conf['proxy_port'] = 8080;
  516. # $conf['proxy_username'] = '';
  517. # $conf['proxy_password'] = '';
  518. # $conf['proxy_user_agent'] = '';
  519. # $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
  520. /**
  521. * Authorized file system operations:
  522. *
  523. * The Update manager module included with Drupal provides a mechanism for
  524. * site administrators to securely install missing updates for the site
  525. * directly through the web user interface. On securely-configured servers,
  526. * the Update manager will require the administrator to provide SSH or FTP
  527. * credentials before allowing the installation to proceed; this allows the
  528. * site to update the new files as the user who owns all the Drupal files,
  529. * instead of as the user the webserver is running as. On servers where the
  530. * webserver user is itself the owner of the Drupal files, the administrator
  531. * will not be prompted for SSH or FTP credentials (note that these server
  532. * setups are common on shared hosting, but are inherently insecure).
  533. *
  534. * Some sites might wish to disable the above functionality, and only update
  535. * the code directly via SSH or FTP themselves. This setting completely
  536. * disables all functionality related to these authorized file operations.
  537. *
  538. * @see http://drupal.org/node/244924
  539. *
  540. * Remove the leading hash signs to disable.
  541. */
  542. # $conf['allow_authorize_operations'] = FALSE;

Comments

I am using haproxy to balance the connections and keepalived to make the haproxy layer itself highly available, this is my configuration:

<?php
$databases
['default']['default'] = array(
 
'driver' => 'mysql',
 
'database' => '<DATABASE_NAME>',
 
'username' => '<USERNAME>',
 
'password' => '<PASSWORD>',
 
'host' => '<WRITE_VIP>',
);
$databases['default']['slave'][] = array(
 
'driver' => 'mysql',
 
'database' => '<DATABASE_NAME>',
 
'username' => '<USERNAME>',
 
'password' => '<PASSWORD>',
 
'host' => '<READ_VIP>',
);
?>

The only piece that I'm not sure of is whether or not Drupal will itself balance the "read" connections between the "default" and "slave" hosts, or if it will send all of them to the "slave" side. In our case, we want it to send all of the read connections to the "slave" (which is already being balanced between all three database nodes). If Drupal does a 1:1 balance between the "default" and "slave" hosts, we will likely end up with two-thirds of the read queries being send to the active write node and one-sixth each being sent to the other two nodes, which greatly diminishes the benefit of moving to the two different connection pools.

Can you help in this matter?