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