Your SlideShare is downloading. ×
0
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Workflow Tools - DrupalCamp Atlanta 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Workflow Tools - DrupalCamp Atlanta 2013

3,191

Published on

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

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,191
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
12
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Workflow Tools Stay Out of Production! Use WF to Deploy Code & Content
  • 2. Derek DeRaps Drupal Developer Mediacurrent @Mediacurrent Yesterday
  • 3. WTF is WFT ?
  • 4. WF is NOT a module.
  • 5. Well… ● ● ● ● ● WF is a module, + much more WF is an approach WF is a method WF is a wrapper @ other tools WF is a new best practice
  • 6. It’s the icing on a 5 layer cake. ● ● ● ● ● Git SSH Drush Jenkins Deploy & UUID modules ○ + many more
  • 7. Who made it, and Why? Dave Hall (Pfizer) Tim Holt (Acquia) Drupal workflow sucks No current “best practice” for deploying content ● New tools maturing ● ● ● ●
  • 8. Pause to watch entire WF presentation from Prague (not really, but do watch it at home!)
  • 9. Old hat.
  • 10. New hotness!
  • 11. “ ” OK THAT’S AWESOME i can haz some??
  • 12. Yes, but don’t muck up your local stack. https://github.com/proviso/proviso
  • 13. STEP 1 of 3 Download the latest “WF Example Profile”
  • 14. STEP 2 of 3 Drupal setup ● ● ● ● ● ● Drush make (must use 5.x) Create “Reply” bundle “job_comment” Enable all wf_example modules Feature-revert all Set variable ‘wf_sandbox_basepath’ Configure git module
  • 15. STEP 3 of 3 Rules → Jenkins jobs ● Rule: After saving a new workflow job ○ Job: create-branch, et cetera... ● Rule: After a job is approved ○ Job: merge-branch ● Rule: After a job is deployed to the final environment ○ Job: delete-sandbox ○ Job: sync-dr ○ Job: prod-snapshot ○ Job: prod-archive ● Rule: After deleting a workflow job ○ Job: delete-sandbox
  • 16. Demo ;)
  • 17. Thank You! Questions? derek.deraps@mediacurrent.com @Mediacurrent Mediacurrent.com slideshare.net/mediacurrent

×