Configuration management has been a hot topic since it was first announced as an initiative. Unfortunately, our dream of being able to save configuration directly to files didn't materialize, and the community has created many complex workflows to work around the problem of storing configuration in the database.
We're programmers and it's time to automate this!
The crux of the difficulty is that Drupal must create and update database schema during configuration import. After working for many months to remove this import step, I happened on a solution that fixes the pain points while still respecting the workflow tools that the community has come to rely on. My answer? Automatic configuration import and export when you need it, and only when you need it with a small development module.
I've called it Config Suite, and it will solve pain points managing configuration during site development. Come talk configuration automation with me, and lets work through the future of config in Drupal 8. You'll leave the session with a more detailed understanding of the steps in configuration management and a tool that will save you time on every site build.