First of all, thanks! I am so glad that you made it up to this point. This chapter was a hands-on training in defining a development workflow. We used a good amount of what is available in Drush core: configuration, shell aliases, commands, and site aliases. Each feature served as a piece of the final puzzle.

We started the chapter by moving our example Drupal project into Drupal Boilerplate, a default directory structure for Drupal projects. We moved all our custom Drush code (configuration, commands, and site aliases) out of Drupal and then added a small piece of code for Drush to discover the new location.

We created a Jenkins job to periodically copy the database and files from the production environment into the development environment. Then, we optimized this process as much as possible by reducing the amount of data that gets downloaded, sanitizing compromising data, and rerouting email submission.

We closed the chapter by offering a way to automate extra tasks to run in local...