settings.local.php 5.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155
  1. <?php
  2. // @codingStandardsIgnoreFile
  3. /**
  4. * @file
  5. * Local development override configuration feature.
  6. *
  7. * To activate this feature, copy and rename it such that its path plus
  8. * filename is 'sites/default/settings.local.php'. Then, go to the bottom of
  9. * 'sites/default/settings.php' and uncomment the commented lines that mention
  10. * 'settings.local.php'.
  11. *
  12. * If you are using a site name in the path, such as 'sites/example.com', copy
  13. * this file to 'sites/example.com/settings.local.php', and uncomment the lines
  14. * at the bottom of 'sites/example.com/settings.php'.
  15. */
  16. /**
  17. * Assertions.
  18. *
  19. * The Drupal project primarily uses runtime assertions to enforce the
  20. * expectations of the API by failing when incorrect calls are made by code
  21. * under development.
  22. *
  23. * @see http://php.net/assert
  24. * @see https://www.drupal.org/node/2492225
  25. *
  26. * If you are using PHP 7.0 it is strongly recommended that you set
  27. * zend.assertions=1 in the PHP.ini file (It cannot be changed from .htaccess
  28. * or runtime) on development machines and to 0 in production.
  29. *
  30. * @see https://wiki.php.net/rfc/expectations
  31. */
  32. assert_options(ASSERT_ACTIVE, TRUE);
  33. \Drupal\Component\Assertion\Handle::register();
  34. /**
  35. * Enable local development services.
  36. */
  37. $settings['container_yamls'][] = DRUPAL_ROOT . '/sites/default/development.services.yml';
  38. /**
  39. * Show all error messages, with backtrace information.
  40. *
  41. * In case the error level could not be fetched from the database, as for
  42. * example the database connection failed, we rely only on this value.
  43. */
  44. $config['system.logging']['error_level'] = 'verbose';
  45. /**
  46. * Disable CSS and JS aggregation.
  47. */
  48. $config['system.performance']['css']['preprocess'] = FALSE;
  49. $config['system.performance']['js']['preprocess'] = FALSE;
  50. /**
  51. * Disable the render cache.
  52. *
  53. * Note: you should test with the render cache enabled, to ensure the correct
  54. * cacheability metadata is present. However, in the early stages of
  55. * development, you may want to disable it.
  56. *
  57. * This setting disables the render cache by using the Null cache back-end
  58. * defined by the development.services.yml file above.
  59. *
  60. * Only use this setting once the site has been installed.
  61. */
  62. $settings['cache']['bins']['render'] = 'cache.backend.null';
  63. /**
  64. * Disable caching for migrations.
  65. *
  66. * Uncomment the code below to only store migrations in memory and not in the
  67. * database. This makes it easier to develop custom migrations.
  68. */
  69. $settings['cache']['bins']['discovery_migration'] = 'cache.backend.memory';
  70. /**
  71. * Disable Internal Page Cache.
  72. *
  73. * Note: you should test with Internal Page Cache enabled, to ensure the correct
  74. * cacheability metadata is present. However, in the early stages of
  75. * development, you may want to disable it.
  76. *
  77. * This setting disables the page cache by using the Null cache back-end
  78. * defined by the development.services.yml file above.
  79. *
  80. * Only use this setting once the site has been installed.
  81. */
  82. $settings['cache']['bins']['page'] = 'cache.backend.null';
  83. /**
  84. * Disable Dynamic Page Cache.
  85. *
  86. * Note: you should test with Dynamic Page Cache enabled, to ensure the correct
  87. * cacheability metadata is present (and hence the expected behavior). However,
  88. * in the early stages of development, you may want to disable it.
  89. */
  90. $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.null';
  91. /**
  92. * Allow test modules and themes to be installed.
  93. *
  94. * Drupal ignores test modules and themes by default for performance reasons.
  95. * During development it can be useful to install test extensions for debugging
  96. * purposes.
  97. */
  98. # $settings['extension_discovery_scan_tests'] = TRUE;
  99. /**
  100. * Enable access to rebuild.php.
  101. *
  102. * This setting can be enabled to allow Drupal's php and database cached
  103. * storage to be cleared via the rebuild.php page. Access to this page can also
  104. * be gained by generating a query string from rebuild_token_calculator.sh and
  105. * using these parameters in a request to rebuild.php.
  106. */
  107. $settings['rebuild_access'] = TRUE;
  108. /**
  109. * Skip file system permissions hardening.
  110. *
  111. * The system module will periodically check the permissions of your site's
  112. * site directory to ensure that it is not writable by the website user. For
  113. * sites that are managed with a version control system, this can cause problems
  114. * when files in that directory such as settings.php are updated, because the
  115. * user pulling in the changes won't have permissions to modify files in the
  116. * directory.
  117. */
  118. $settings['skip_permissions_hardening'] = TRUE;
  119. /**
  120. * Exclude modules from configuration synchronization.
  121. *
  122. * On config export sync, no config or dependent config of any excluded module
  123. * is exported. On config import sync, any config of any installed excluded
  124. * module is ignored. In the exported configuration, it will be as if the
  125. * excluded module had never been installed. When syncing configuration, if an
  126. * excluded module is already installed, it will not be uninstalled by the
  127. * configuration synchronization, and dependent configuration will remain
  128. * intact. This affects only configuration synchronization; single import and
  129. * export of configuration are not affected.
  130. *
  131. * Drupal does not validate or sanity check the list of excluded modules. For
  132. * instance, it is your own responsibility to never exclude required modules,
  133. * because it would mean that the exported configuration can not be imported
  134. * anymore.
  135. *
  136. * This is an advanced feature and using it means opting out of some of the
  137. * guarantees the configuration synchronization provides. It is not recommended
  138. * to use this feature with modules that affect Drupal in a major way such as
  139. * the language or field module.
  140. */
  141. # $settings['config_exclude_modules'] = ['devel', 'stage_file_proxy'];