Your SlideShare is downloading. ×
0
Features: safely deploying your site João Ventura (jcnventura) [email_address]
Site resources <ul><li>Moving a Drupal site usually requires the following three sets of resources: </li><ul><li>Drupal co...
Lorem Ipsum content (irrelevant) </li></ul></ul></ul>
The problem <ul><li>The configuration changes created in the Drupal database are part of the development process. </li><ul...
Config should be handled in the same VCS that manages the code
It should be possible to propagate changes from development to production (specially for a live site) </li></ul></ul>
Content types / CCK <ul><li>Managing a content type: </li><ul><li>DB-only
Content copy module
hook_node_info()
or...
Features module </li></ul></ul>
What does Features do <ul>” Features provides a UI and API for taking different site building components from modules with...
Features puts configuration into code
Upcoming SlideShare
Loading in...5
×

Features: safely deploying your site

688

Published on

Slides from my Drupalcamp Lisbon 2011 session.

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

  • Be the first to like this

No Downloads
Views
Total Views
688
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Features: safely deploying your site"

  1. 1. Features: safely deploying your site João Ventura (jcnventura) [email_address]
  2. 2. Site resources <ul><li>Moving a Drupal site usually requires the following three sets of resources: </li><ul><li>Drupal code files </li><ul><li>usually managed under a VCS </li></ul><li>Data files (i.e. sites/default/files/*) </li><ul><li>Usually not relevant when moving from development to production, as it is full of placeholder images </li></ul><li>Drupal database </li><ul><li>Changes to configuration (important)
  3. 3. Lorem Ipsum content (irrelevant) </li></ul></ul></ul>
  4. 4. The problem <ul><li>The configuration changes created in the Drupal database are part of the development process. </li><ul><li>Moving config should not move test content
  5. 5. Config should be handled in the same VCS that manages the code
  6. 6. It should be possible to propagate changes from development to production (specially for a live site) </li></ul></ul>
  7. 7. Content types / CCK <ul><li>Managing a content type: </li><ul><li>DB-only
  8. 8. Content copy module
  9. 9. hook_node_info()
  10. 10. or...
  11. 11. Features module </li></ul></ul>
  12. 12. What does Features do <ul>” Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its .info file so that it can be checked, updated, or reverted programmatically.” </ul>
  13. 13. Features puts configuration into code
  14. 14. Exportables support in Features <ul><li>Content types
  15. 15. CCK fields / fieldgroups
  16. 16. Views
  17. 17. Imagecache
  18. 18. Input filters
  19. 19. Users roles / permissions
  20. 20. CTools export API </li><ul><li>Panels
  21. 21. Open Layers </li></ul></ul>
  22. 26. Resources <ul><li>Features module </li><ul><li>http://drupal.org/project/features </li></ul><li>Strongarm module (variables export) </li><ul><li>http://drupal.org/project/strongarm </li></ul><li>Features extra </li><ul><li>http://drupal.org/project/features_extra </li></ul></ul>
  23. 27. Questions <ul><li>Thanks to Florian Lorétan of wunderkraut for some of the slides </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×