- 1. Features: safely deploying your site Joo Ventura
(jcnventura) [email_address]
2. Site resources
- Moving a Drupal site usually requires the following three sets
of resources:
- Drupal code files
- usually managed under a VCS
- Data files (i.e. sites/default/files/*)
- Usually not relevant when moving from development to
production, as it is full of placeholder images
- Drupal database
- Changes to configuration (important) 3. Lorem Ipsum content
(irrelevant)
4. The problem
- The configuration changes created in the Drupal database are
part of the development process.
- Moving config should not move test content 5. Config should be
handled in the same VCS that manages the code 6. It should be
possible to propagate changes from development to production
(specially for a live site)
7. Content types / CCK
- Managing a content type:
- DB-only 8. Content copy module 9. hook_node_info() 10. or...
11. Features module
12. What does Features do
- 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.
13. Features puts configuration into code 14. Exportables
support in Features
- Content types 15. CCK fields / fieldgroups 16. Views 17.
Imagecache 18. Input filters 19. Users roles / permissions 20.
CTools export API
22. 23. 24. 25. 26. Resources
- Features module
- http://drupal.org/project/features
- Strongarm module (variables export)
- http://drupal.org/project/strongarm
- Features extra
- http://drupal.org/project/features_extra
27. Questions
- Thanks to Florian Lortan of wunderkraut for some of the
slides