Your SlideShare is downloading. ×
Code Driven Development Zaporozhye DrupalForum
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

Code Driven Development Zaporozhye DrupalForum

8,904
views

Published on

Presentation about Code Driven Development

Presentation about Code Driven Development

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
8,904
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
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. Yuriy Gerasimov Madcap B.V. [email_address] skype yuriy_gerasimov Code Driven Development
  • 2. Problems in development
    • Distributed team workflow
    • 3. No separation from content
    • 4. Pushing changes to Staging / Production
    • 5. No version control
  • 6. Benefits to keep all settings in code
    • Version control
    • 7. Resolving conflicts between developers
    • 8. Push settings between installations (to production)
    • 9. See if client didn’t change anything
    • 10. Keep client’s testing data on staging site
  • 11. Step 1: Installation profile
    • Add all needed modules, and Controller module
  • 12. Step 2: Use features where possible
    • Variables (strongarm)
    • 13. Content types (all CCK fields settings)
    • 14. Views
    • 15. Panels
    • 16. Imagecache presets
    • 17. Blocks visibility (context)
  • 18. Creating feature
  • 19. Step 3: All changes in Controller module
    • features_install_modules(array('views'));
    • 20. create some node, taxonomy, users space
    • 21. create node, term
  • 22. Step 4: Workflow hook_update_N()
  • 23. Workflow
  • 24. Workflow. New developer joins the team
  • 25. Workflow. Also add changes to hook_install()
  • 26. Features Namespace # Feature News (feature_news) Views feature_news_blocks feature_news_list feature_news_node feature_news_taxonomy Contexts feature_news_front feature_news_list CCK Fields field_news_pictures field_news_links Imagecache Presets news-s news-m news-l news-portrait
  • 27. Drush features
  • 28. Drush
    • From code to database
      • drush features-revert _feature_name_
      • 29. drush features-revert-all
    • From database to code
      • drush features-update _feature_name_
      • 30. drush features-update-all
    • Diff (need to install diff module)
  • 31. Drush features-diff _feature_name_
  • 32. Release to staging / production
    • release the code
    • 33. drush updatedb – run all updates
    • 34. drush features-revert-all – update settings from features
    • 35. drush cc – clear caches
  • 36. Resources
    • http://nuvole.org/blog/2010/aug/24/features-based-development-workflow
    • 37. http://drupal.org/project/features
    • 38. http://drupal.org/project/kit
  • 39. Future
    • Feature-branch development for site development
  • 40. Yuriy Gerasimov Madcap B.V. [email_address] skype yuriy_gerasimov twitter @ygerasimov Code Driven Development Thanks!