These are my notes when doing my first (drupal) presentation @ FrOSCon 2008 Drupal Room
This method uses the concepts
This way an upgrade to another drupal version runs smoothly. Hmmm this was about developer environment.
Why do I need this? To make sites like http://nf.test http://nf.dev or http://froscon.demo
sudo su -
echo 127.0.0.254 froscon.demo >> /etc/hosts
I've build a few drupal modules. Mosts modules are paid for.
I don't like the idea that dependencies are not handled in a unified way. By that I mean that both module.inc and update.php code is written to handle module status. There should be a central library handling their dependencies. When we handle this in a unified way installing a big project like ubercart is easy.
When installing/enabling a module it is important to know what this module is dependent of. Ie uc_cart is dependent of uc_order. See ie http://build2be.com/sites/build2be.com/files/ubercart.neato.png
The title of this page should be project management because Drupal uses projects for delivering modules.
A companion video shows the Drupal 5.x situation. Using drush, my drush_mm patch and update status to manage and install modules command line. This video shows better dependency checking than currently available in D7. As I hope is clear I want to contribute to implement this into D7.
It's quite neat using drush to install ubercart. Here is what I did.
Preparation
Installing