settings.php, but the setting names and values are very inconsistent.default.settings.php).Note: This list may be incomplete.
| Setting | Value | Usage |
|---|---|---|
| diff_context_lines_leading | integer | |
| diff_context_lines_trailing | integer | |
| php_storage | array map of bin (or "default") to storage config | PhpStorageFactory::get() |
| cache | array map of bin (or "default") to service ID | CacheFactory::get() |
| drupal_bootstrap_config_storage | callable (Config\StorageInterface) | BootstrapConfigStorageFactory::get() |
| extension_discovery_scan_tests | boolean | #2198713: Add a settings.php variable to allow to discover/enable test extensions at regular runtime |
| keyvalue_service_[collection] | service ID | KeyValueFactory::get() |
| keyvalue_default | service ID | KeyValueFactory::get() |
| queue_reliable_service_[queue] | service ID | QueueFactory::get() |
| queue_service_[queue] | service ID | QueueFactory::get() |
| queue_default | service ID | QueueFactory::get() |
| $conf['container_service_providers'] | array map of "name" to FQCN | DrupalKernel::discoverServiceProviders() |
| $conf['container_yamls'] | array of service yaml filepaths | DrupalKernel::discoverServiceProviders() |
| yaml_parser_class | FQCN | #1920902: Add a Drupal Yaml wrapper so we can default to PECL Yaml component if it is available |
/**
* ...
*
* @setting array cache
* An associative array whose keys are cache bins and whose values
* are service IDs. If the requested cache bin is not defined, then
* the 'default' bin key is checked. Defaults to 'cache.backend.database'.
*/
class CacheFactory extends ContainerAware {
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | settings.php-2160705-6.patch | 76.91 KB | mgifford |
Comments
Comment #1
sunComment #2
sunFWIW, #1757536: Move settings.php to /settings directory, fold sites.php into settings.php moves the default settings file into
/core/default.settings.phpBased on that, I wonder whether we couldn't have two separate files, like this?
The advanced file would allow us to document all of the internal/hidden settings that are mentioned in the OP. At the same time, we can move more advanced settings from the default file into the advanced file, so as to end up with ~10KB instead of the current 30+KB :-)
Comment #3
sunAdding #2198713: Add a settings.php variable to allow to discover/enable test extensions at regular runtime
Comment #4
Crell commented+14,912 to #2. Whether we move the files or not, our current settings.php file is so huge it's almost unusable.
Comment #5
sunComment #6
mgiffordJust to get things rolling on this issue. Here's a patch that I think addresses #2.
Doesn't address the more important elements here, but hoping to nudge this along. A smaller default should be much easier for people to navigate.
There are some other inconsistencies in the default.settings.php that could be cleaned up too.
Comment #9
jibranHow is this a bug?
Comment #23
quietone commentedThis issue was discussed at a Bug Smash Initiative group triage meeting, with both darvanen and larowlan adding to the discussion. As a result some of the related/child issue have been closed.
The scope of this issue results in a large documentation patch covering many areas of settings.php. This issue should be a Meta with work done on the various topics done in smaller child issue. Adding tags for re scoping and issue summary update.
We did not review the existing patch for accuracy or if the suggested changes have already been made.
Adding credit for triage