Using Drupal As A Web Framework
Drupal promotes configurability. Even though many modules now provide site building infrastructure and building blocks rather than specific functionality (and even those targeting specific use cases are often highly configurable), this tendency leads to a paradigm that treats development and deployment of drupal as primarily a problem of configuration management.
Recent interest in distributions and improved awareness of site management best practices reveal another way of thinking about developing a Drupal site as a "proper" web application and treating Drupal as a framework.
This session will show why you may not want to duplicate every bit of contributed code in your version control repository, why sites/all or sites/default is not always the best location for module and theme code, what a real build and deploy system might look like (and how it changes site building and other development workflows) and why you might not be running enough instances of your application (hint: local/dev and production probably aren't enough). Examples of a multi-developer, code-only approach to development with drush make will be demoed.
Technology - drush, aegir, drush_make, shell scripting, drupal 6, drupal 7
- framework or CMS, what's the difference?
- defining the parts (profiles, instances, make files, etc.)
- code-only development
- update functions
- what to do with troublesome modules
- an example build system built on drush make
- a bonus side effect of this approach (increased community patch contributions)