Keeping code and configuration together is one of the most important challenges in a Drupal project. In this chapter, we covered a strategy to accomplish this challenge, using a script that we called the update path. Next, we went through each of its steps in detail, explaining some useful scenarios in order to gain further insight into what these are meant to accomplish.

We started by explaining what Drupal's registry is and how to make sure that it does not break while bootstrapping, using the registry-rebuild Drush command. We actually broke the registry of a sample Drupal project and demonstrated how Registry Rebuild can get it back to work.

The next step in the update path discussed running database updates. We wrote a custom database update on a module and then executed it using Drush. The last step on the update path consisted of importing configuration using the Features module. Thanks to the Features module, we are able to export all sorts of configuration from a Drupal project...