Misusing...er...uh... Re-purposing Recipes to achieve development bliss
Misusing...er...uh... Re-purposing Recipes to achieve development bliss
I want...
- Drupal CMS
- Configuration management
- Automatic updates
- Git workflows
- Modern infrastructure
- Continuous delivery
- Project Browser for content editors
In the words of Queen, "I want it all... and I want it now!"
Drupal's configuration management has evolved from strictly living in the database to becoming entities that can be exported, imported and validated. The strict management of configuration in code has me longing for the days where we just let the database handle it all.
With the rise of Drupal CMS, configuration management becomes even more challenging. How do we allow content editors and site administrators the ability to configure their site without having a deployment pipeline config:import and blow away those changes?
Can we have our configuration management and our modern workflows?