Content management systems allow administrators and developers to change settings in the User Interface (UI).
These settings, or configurations are stored in the database.
Exporting them to code allows us to manage them in version control for backups, and across servers for development and testing, without having to have the actual database.
Configuration management is moving things from the database to code.
Save valuable time (and sanity) by bypassing the process of picking and choosing which components go into which Features.
Features Builder is a module that analyzes the build of your Drupal site and automatically builds Feature modules to capture the site's configuration.
The main functionality is built around the idea of a "builder" which is responsible for identifying what configuration it's responsible for.
Various administrative screens allow you to see what's available on your site, how the builders will package your configuration, and one-click operation to generate and install the Features modules.
Drupal 7 to work from the code in the features modules, configuration in the database, or both.
The Features revert
drush fra would allow you to say ignore the database, and use code, but would not empty the database.
drush fra --force would force the emptying of the database, so it would have to use the code.
Unlike Drupal 8 configuration which in which config is imported/exported from the database.
Once you have the database empty, and the functionality in code, you can turn off the feature, rebuild the functionality, so it can be exported later.
drush fb -y
After you deploy, add
drush fra -y --force to your CI or run it manually.
Special thanks to Damon, Morgan, Savino, Adam, Shiraz, and Matthew for the photography!