Config to Code

Thoughts on Configuration Management

This is a sketch of how some of the ideas discussed in the core conversations configuration management sessions yesterday might look in practice. Obviously this is just one idea and there are plenty of other valid approaches (overall of for any specific piece) - we don't want to get too specific yet. For example, some of what I describe could probably happily live in contrib. I think my big picture point is that the approaches discussed are not mutually exclusive, and in fact we probably need bits of each of them.

Config To Code Module Is Like Features For Drupal 5

Config to Code module for Drupal 5 makes it easy to deploy new views and panels and to version-control changes to existing ones with a source code repository like subversion. It makes it quick and easy to move configured views and panels in the database to code, then safely delete the configured views from the database and finally, expose the views and panels in code back to their respective modules. It is extensible for other types of configurations that can be stored both in database and code.

Read on for the demo screencast.
Syndicate content