example.settings.local.php 3.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. <?php
  2. /**
  3. * @file
  4. * Local development override configuration feature.
  5. *
  6. * To activate this feature, copy and rename it such that its path plus
  7. * filename is 'sites/default/settings.local.php'. Then, go to the bottom of
  8. * 'sites/default/settings.php' and uncomment the commented lines that mention
  9. * 'settings.local.php'.
  10. *
  11. * If you are using a site name in the path, such as 'sites/example.com', copy
  12. * this file to 'sites/example.com/settings.local.php', and uncomment the lines
  13. * at the bottom of 'sites/example.com/settings.php'.
  14. */
  15. /**
  16. * Assertions.
  17. *
  18. * The Drupal project primarily uses runtime assertions to enforce the
  19. * expectations of the API by failing when incorrect calls are made by code
  20. * under development.
  21. *
  22. * @see http://php.net/assert
  23. * @see https://www.drupal.org/node/2492225
  24. *
  25. * If you are using PHP 7.0 it is strongly recommended that you set
  26. * zend.assertions=1 in the PHP.ini file (It cannot be changed from .htaccess
  27. * or runtime) on development machines and to 0 in production.
  28. *
  29. * @see https://wiki.php.net/rfc/expectations
  30. */
  31. assert_options(ASSERT_ACTIVE, TRUE);
  32. \Drupal\Component\Assertion\Handle::register();
  33. /**
  34. * Enable local development services.
  35. */
  36. $settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml';
  37. /**
  38. * Show all error messages, with backtrace information.
  39. *
  40. * In case the error level could not be fetched from the database, as for
  41. * example the database connection failed, we rely only on this value.
  42. */
  43. $config['system.logging']['error_level'] = 'verbose';
  44. /**
  45. * Disable CSS and JS aggregation.
  46. */
  47. $config['system.performance']['css']['preprocess'] = FALSE;
  48. $config['system.performance']['js']['preprocess'] = FALSE;
  49. /**
  50. * Disable the render cache (this includes the page cache).
  51. *
  52. * Note: you should test with the render cache enabled, to ensure the correct
  53. * cacheability metadata is present. However, in the early stages of
  54. * development, you may want to disable it.
  55. *
  56. * This setting disables the render cache by using the Null cache back-end
  57. * defined by the development.services.yml file above.
  58. *
  59. * Do not use this setting until after the site is installed.
  60. */
  61. # $settings['cache']['bins']['render'] = 'cache.backend.null';
  62. /**
  63. * Disable Dynamic Page Cache.
  64. *
  65. * Note: you should test with Dynamic Page Cache enabled, to ensure the correct
  66. * cacheability metadata is present (and hence the expected behavior). However,
  67. * in the early stages of development, you may want to disable it.
  68. */
  69. # $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.null';
  70. /**
  71. * Allow test modules and themes to be installed.
  72. *
  73. * Drupal ignores test modules and themes by default for performance reasons.
  74. * During development it can be useful to install test extensions for debugging
  75. * purposes.
  76. */
  77. $settings['extension_discovery_scan_tests'] = TRUE;
  78. /**
  79. * Enable access to rebuild.php.
  80. *
  81. * This setting can be enabled to allow Drupal's php and database cached
  82. * storage to be cleared via the rebuild.php page. Access to this page can also
  83. * be gained by generating a query string from rebuild_token_calculator.sh and
  84. * using these parameters in a request to rebuild.php.
  85. */
  86. $settings['rebuild_access'] = TRUE;
  87. /**
  88. * Skip file system permissions hardening.
  89. *
  90. * The system module will periodically check the permissions of your site's
  91. * site directory to ensure that it is not writable by the website user. For
  92. * sites that are managed with a version control system, this can cause problems
  93. * when files in that directory such as settings.php are updated, because the
  94. * user pulling in the changes won't have permissions to modify files in the
  95. * directory.
  96. */
  97. $settings['skip_permissions_hardening'] = TRUE;