Configuration Management for Backdrop CMS

Backdrop CMS is essentially Drupal 7 plus a Configuration Management System (and a few hundred other improvements).

Configuration Management is done differently in Backdrop CMS than it is in modern versions of Drupal. Come learn about Configuration Management in Backdrop, including:

• What is configuration management, and why do we need it?
• Comparing changes in configuration using the Configuration Management Interface
• how to deploy Configuration changes using the Configuration Management Interface
• Comparing changes in configuration using git diff
• how to deploy Configuration changes using git
• Best practices for how to manage configuration simply
• Best practices for how to manage configuration for multiple developers
• Best practices for how to manage configuration for multiple instances of your website (for example: on Pantheon)
• Coning soon: How to use configuration sets, or "Recipes"
• Coming soon: the "Features" module for Backdrop (using Configuration)

Backdrop's Configuration Management System is my favorite improvement because it saves me so much time during maintenance, upgrades, and site builds.

RELATED ARTICLES

• Figure-8 approach (simple: works best for 1 developer, 1 production site)
  https://www.jenlampton.com/blog/managing-backdrop-cms-config-files-git
• Versioned staging directory approach: (moderate, works best for multiple devs, 1 production site)
  https://www.jenlampton.com/blog/backdrop-cms-configuration-files-and-git...
• Versioned staging, with multiple active directories (complex: best for Pantheon, multiple production sites)
  https://www.jenlampton.com/blog/move-your-backdrop-site-to-pantheon