automation

The install script configures the LAMP stack for drupal, installs APC, drush, drush make and sets up a database for our drupal. After this we launch the make file which downloads all needed code for our drupal. Now the script will configure the drupal file system, set up the permissions and copy the drupal install profile and resources.

(Wouldn't have linked, except they also linked to Drubuntu and others so they clearly did their research.)

<

blockquote>This demonstrates four different methods for downloading code, from three different sources.

To execute, install Drush, install Drush Make, then run the attached file [...t]o specify an output directory, add the path as an extra parameter:

drush make search.make /var/www

I have written one of my 'build' files (make files) that grabs Drupal core and my install profile from git.mig5.net:

core = 6.x
projects[] = drupal
projects[feature_server][type] = "profile"
projects[feature_server][download][type] = "git"
projects[feature_server][download][url] = "git://git.mig5.net/drupal/profiles/feature_server"

As always, the install profile itself, once cloned from git, contains its own make file that grabs all the other components and puts them into place. It's based on Young's own featureserver.make file