Universal configuration storage
Drupal 8’s configuration system handles all kinds of config settings, and you have options for how and where you store your data. By default, both global and itemized settings are stored, in a standard format, in the database. But you can change that. Choose Drupal UI, Drush, or file-based workflows. You can also export your config data into YAML files to manage it with version control. And, if you need to, you can override config data in your settings.php file.
Drupal.org is generously sponsored by companies like:
Create on Drupal 8 with 1&1’s new cloud technology, you get dedicated resources that are scalable on demand with by-the-minute billing. Best price-performance ratio and a risk-free $50 credit
For better deployments
You’ve learned—theoretically, or the hard way—to be very careful about making configuration changes on live sites. But exporting and importing settings between environments hasn’t exactly been simple. Now, you can move production-ready data out of development or staging more fluidly. Drupal includes support for generating and validating universally unique identifiers (UUID) to sync configuration between instances of the same site. If two environments have the same UUID, Drupal 8 makes it easier to deploy single or full-export configuration changes from one to the other (and back again).
And for better maintenance
The new configuration tools aren’t just for launches and roll-outs. A lot of work happens before and after pushing changes live. That’s why Drupal supports configuration schema, dependencies, and validation in all your environments: so you can maintain data-integrity between deployments and updates. Trust that most dependencies are dynamically calculated and declared automatically. Use schema to automate config entity persistence and the generation of the config translation UI.