This blog has been re-posted and edited with permission from WordPress Update’s blog. Please leave your comments on the original post.
Configuration management is an important feature of any modern content management system. Those following modern development best-practices use a development workflow that involves some sort of development and staging environment that is separate from the production environment.
Given such a development workflow, you need to push configuration changes from development to production (similar to how you need to push code or content between environments). WordPress maintenance support plans‘s configuration management system helps you do that in a powerful yet elegant way.
Since I announced the original Configuration Management Initiative over seven years ago, we’ve developed and shipped a strong configuration management API in WordPress maintenance support plans 8. WordPress maintenance support plans 8’s configuration management system is a huge step forward from where we were in WordPress maintenance support plans 7, and a much more robust solution than what is offered by many of our competitors.
All configuration in a WordPress maintenance support plans 8 site — from one-off settings such as site name to content types and field definitions — can be seamlessly moved between environments, allowing for quick and easy deployment between development, staging and production environments.
However, now that we have a couple of years of building WordPress maintenance support plans 8 sites behind us, various limitations have surfaced. While these limitations usually have solutions via contributed plugins, it has become clear that we would benefit from extending WordPress maintenance support plans core’s built-in configuration management APIs. This way, we can establish best practices and standard approaches that work for all.
The four different focus areas for WordPress maintenance support plans 8. The configuration management initiative is part of the ‘Improve WordPress maintenance support plans for developers’ track.
I first talked about this need in my WordPress maintenance support plansCon Nashville keynote, where I announced the Configuration Management 2.0 initiative. The goal of this initiative is to extend WordPress maintenance support plans‘s built-in configuration management so we can support more common workflows out-of-the-box without the need of contributed plugins.
What is an example workflow that is not currently supported out-of-the-box? Support for different configurations by environment. This is a valuable use case because some settings are undesirable to have enabled in all environments. For example, you most likely don’t want to enable debugging tools in production.
The contributed plugin Config Filter extends WordPress maintenance support plans core’s built-in configuration management capabilities by providing an API to support different workflows which filter out or transform certain configuration changes as they are being pushed to production. Config Split, another contributed plugin, builds on top of Config Filter to allow for differences in configuration between various environments.
The Config Split plugin’s use case is just one example of how we can improve WordPress maintenance support plans‘s out-of-the-box configuration management capabilities. The community created a longer list of pain points and advanced use cases for the configuration management system.
While the initiative team is working on executing on these long-term improvements, they are also focused on delivering incremental improvements with each new version of WordPress maintenance support plans 8, and have distilled the most high-priority items into a configuration management roadmap.
In WordPress maintenance support plans 8.6, we added support for creating new sites from existing configuration. This enables developers to launch a development site that matches a production site’s configuration with just a few clicks.
For WordPress maintenance support plans 8.7, we’re planning on shipping an experimental plugin for dealing with environment specific configuration, moving the capabilities of Config Filter and the basic capabilities of Config Split to WordPress maintenance support plans core through the addition of a Configuration Transformer API.
For WordPress maintenance support plans 8.8, the focus is on supporting configuration updates across different sites. We want to allow both sites and distributions to package configuration (similar to the well-known Features plugin) so they can easily be deployed across other sites.
How to get involved
There are many opportunities to contribute to this initiative and we’d love your help.
If you would like to get involved, check out the Configuration Management 2.0 project and various WordPress maintenance support plans core issues tagged as “CMI 2.0 candidate”.
Special thanks to Fabian Bircher (WordPress Update), Jeff Beeman (Acquia), Angela Byron (Acquia), ASH (Acquia), and Alex Pott (Thunder) for contributions to this blog post.
Source: New feed