Why manage configuration?
It's simple to explain why configuration that is only saved in the database is bad. You can't keep track of any changes (who made what change, and when); it's hard to work with a group of people (you simply can't get their changes without using their SQL dump, and using their dump would delete your work); and, if you build something on a development environment, how do you get it to the live site? You get the gist. We want our configuration in files, and Drupal 8 gives us just that.
Before Drupal 8, a variety of methods were used to transport configuration from one environment to another—for example, from a development environment to a production environment.
These included some rather bad methods such as writing down the ...
Get Drupal 8 Configuration Management now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
