In DrupalCon we had BoF about DOG and aspect of configuration management (later CM) came up.
What we need to do related to configuration management is to decide what are our goals.
What i mean by configuration management is that when site is being deployed to certain (or several) server (local dev, testing, live...) DOG can make needed changes in order to apply those settings. If you understand configuration management differently or have different need/use case for CM give us your opinion.
So basically there are (attleast) two open question.
First what settings should be part of CM?
Meaning
- settings.php
* database
* cookie domain
* reverse proxy
* site url
* memcache?
* way for add own custom settings?
- settings saved in database
* maintenance mode
* logging and errors
* performance settings
* clean url's
* also way to define certain settings for your favourite module?
Secondly what kind of interface you would prefer for editing these settings?
- text / xml file
* propably easiest view for all the settings allready in plase and view what is incorrect
- command line (terminal) parameters aka "drush dog config @live siteurl http://example.com"
- both ?
Everthing is ofcourse matter of balance between features and complexity but what's your opinion?