3 // @codingStandardsIgnoreFile
7 * Local development override configuration feature.
9 * To activate this feature, copy and rename it such that its path plus
10 * filename is 'sites/default/settings.local.php'. Then, go to the bottom of
11 * 'sites/default/settings.php' and uncomment the commented lines that mention
12 * 'settings.local.php'.
14 * If you are using a site name in the path, such as 'sites/example.com', copy
15 * this file to 'sites/example.com/settings.local.php', and uncomment the lines
16 * at the bottom of 'sites/example.com/settings.php'.
22 * The Drupal project primarily uses runtime assertions to enforce the
23 * expectations of the API by failing when incorrect calls are made by code
26 * @see http://php.net/assert
27 * @see https://www.drupal.org/node/2492225
29 * If you are using PHP 7.0 it is strongly recommended that you set
30 * zend.assertions=1 in the PHP.ini file (It cannot be changed from .htaccess
31 * or runtime) on development machines and to 0 in production.
33 * @see https://wiki.php.net/rfc/expectations
35 assert_options(ASSERT_ACTIVE, TRUE);
36 \Drupal\Component\Assertion\Handle::register();
39 * Enable local development services.
41 $settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml';
44 * Show all error messages, with backtrace information.
46 * In case the error level could not be fetched from the database, as for
47 * example the database connection failed, we rely only on this value.
49 $config['system.logging']['error_level'] = 'verbose';
52 * Disable CSS and JS aggregation.
54 $config['system.performance']['css']['preprocess'] = FALSE;
55 $config['system.performance']['js']['preprocess'] = FALSE;
58 * Disable the render cache.
60 * Note: you should test with the render cache enabled, to ensure the correct
61 * cacheability metadata is present. However, in the early stages of
62 * development, you may want to disable it.
64 * This setting disables the render cache by using the Null cache back-end
65 * defined by the development.services.yml file above.
67 * Only use this setting once the site has been installed.
69 # $settings['cache']['bins']['render'] = 'cache.backend.null';
72 * Disable caching for migrations.
74 * Uncomment the code below to only store migrations in memory and not in the
75 * database. This makes it easier to develop custom migrations.
77 # $settings['cache']['bins']['discovery_migration'] = 'cache.backend.memory';
80 * Disable Internal Page Cache.
82 * Note: you should test with Internal Page Cache enabled, to ensure the correct
83 * cacheability metadata is present. However, in the early stages of
84 * development, you may want to disable it.
86 * This setting disables the page cache by using the Null cache back-end
87 * defined by the development.services.yml file above.
89 * Only use this setting once the site has been installed.
91 # $settings['cache']['bins']['page'] = 'cache.backend.null';
94 * Disable Dynamic Page Cache.
96 * Note: you should test with Dynamic Page Cache enabled, to ensure the correct
97 * cacheability metadata is present (and hence the expected behavior). However,
98 * in the early stages of development, you may want to disable it.
100 # $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.null';
103 * Allow test modules and themes to be installed.
105 * Drupal ignores test modules and themes by default for performance reasons.
106 * During development it can be useful to install test extensions for debugging
109 # $settings['extension_discovery_scan_tests'] = TRUE;
112 * Enable access to rebuild.php.
114 * This setting can be enabled to allow Drupal's php and database cached
115 * storage to be cleared via the rebuild.php page. Access to this page can also
116 * be gained by generating a query string from rebuild_token_calculator.sh and
117 * using these parameters in a request to rebuild.php.
119 $settings['rebuild_access'] = TRUE;
122 * Skip file system permissions hardening.
124 * The system module will periodically check the permissions of your site's
125 * site directory to ensure that it is not writable by the website user. For
126 * sites that are managed with a version control system, this can cause problems
127 * when files in that directory such as settings.php are updated, because the
128 * user pulling in the changes won't have permissions to modify files in the
131 $settings['skip_permissions_hardening'] = TRUE;