Presentation video now available! https://www.drupalcampatlanta.com/session/stay-out-production-use-workflow-tools-deploy-your-content-and-code …
Presentation video now available! https://www.drupalcampatlanta.com/session/stay-out-production-use-workflow-tools-deploy-your-content-and-code
STOP creating content in production.
DON'T be limited by a single content server.
USE wf tools to deploy your content.
Wouldn't it be nice to deploy database (content/config) changes the same way you deploy code? (You should be nodding your head). With WF Tools, both content creators and developers start their changes by logging into a WF Tools "management instance" to create a new "job." WF Tools then uses Jenkins and other server-side tools to spin up a new site (e.g., job1.example.com) with its own git branch (think: git-flow "feature"). All content changes are tracked so that, when the job is finished, WF Tools can move them to a staging server via the Deploy module, and the git branch is merged into the staging branch. The same process happens when the changes are ready for production. The mantra is: many small jobs > fewer large ones!
At DrupalCon Prague, Dave Hall (WF Tools maintainer) and Tim Holt (of Acquia) presented on the WF Tools module, which has the potential to revolutionize content deployment as we know it. I recommend you watch the DrupalCon Prague presentation, and then come to this one for more details and discussion of implementation best practices. This presentation is geared toward developers, devops, and site builders of medium- to enterprise-level websites.
Read more at drupal.org/project/wf