{"comment":{"user":{"login":"MarFarMa","id":27477,"url":"https://api.github.com/users/MarFarMa","avatar_url":"https://secure.gravatar.com/avatar/3970ddf2027b9b83969a233e2b389a84?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3970ddf2027b9b83969a233e2b389a84"},"created_at":"2011-12-28T18:27:47Z","path":null,"updated_at":"2011-12-28T18:27:47Z","id":824722,"html_url":"https://github.com/MarFarMa/wp-cli/commit/dcc129348e#commitcomment-824722","position":null,"body":"It's human editable.  Serialized options can be easily modified, with the migration/import function re-packaging the values as needed.  \r\n\r\nAnd a YAML file can contain PHP code that is evaluated just before parsing.  I'm not sure that I'll need that feature immediately -- but I like having the option.\r\n\r\nI've reverted my changes to the plugin.php file and will be adding a community command DbMigration.  It enables the generation of migration templates for core, plugin, and theme settings - with specific migrations functionality defined via hooks.\r\n\r\nThe generated migration template can be edited and separated into staging targets as desired.   The migration files can be placed under source code control and participate in a capistrano deploy -- so I can deploy to UAT and migrate with UAT settings, and deploy to production and migrate with the production settings.  It's meant to address this: http://wordpress.stackexchange.com/questions/24314/wordpress-database-synch-between-dev-and-prod/24982#24982","url":"https://api.github.com/repos/MarFarMa/wp-cli/comments/824722","commit_id":"dcc129348e11efdf14d0630ce9aa53daa019d2fa","line":null}}