Demo Framework Distribution Installation

Here are some helpful ways that you can install and run the Demo Framework.

You can download the packaged releases and install as you normally would but you might need to increase some php.ini settings for the install to run properly.

There are also some advanced techniques used to ease installation of the distribution.

For example, using Vagrant means you can test deployments on the exact same environment as the DF maintainers. The idea is that we can much more easily collaborate and solve people's problems if we use a shared box. For full instructions, see Demo Framework with Vagrant.

Another great way to get going is by using the Drupal Ant project for Apache Ant to build DF. Apache Ant is a Java library and command-line tool for for automating software build processes.

You can also get a local install going in a few short minutes by using Demo Framework on Acquia Dev Desktop.

Finally, if you've got a boutique Homebrew setup, using MAMP, or just plain old Linux, you might find our automated build script to be a handy tool for provisioning a fresh copy of Demo Framework.

Comments

thanny’s picture

If you get Progress object failure: NS_ERROR_CALL_FAILED, don't use Virtualbox 4.2.14 - use 4.2.12 instead (discussion).

This got me past this error, but I subsequently hit a similar version incompatibility with Chef. It seems that there is a magic combination of versions of the various pieces to use, at least for now. It would be helpful if there was a list of known-good combinations of Virtualbox, Vagrant, etc to install.

saltednut’s picture

I've had issues similar to this too. Its difficult to track this since VirtualBox, Vagrant and Chef are moving targets.

Right now, I am running:

OS X 10.9.1 Mavericks
VirtualBox 4.3.6 for OS X hosts
Vagrant 1.4.3
Vagrant Berkshelf 1.3.7
Vagrant Omnibus 1.2.1

In order to get everything working, I had to switch boxes. The Drupal Cookbook we have been using was updated, and the authors recommended using an Opscode base box, Debian Wheezy, from https://github.com/opscode/bento.

Due to the new box, I had to make some changes to the Berksfile. Specifically, providing a MySQL recipe. Since the bento boxes do not ship with anything extra, I also needed to update the Vagrantfile, installing Chef (via Ombinus) and invoking all the correct recipes. The last step was updating the Vagrantfile to be compatible with the new version of the drupal_cookbook. Once this was sorted, everything pretty much fell back into place.

I've updated the docs for DF to reflect these changes - these have been moved to their own page. The public gists the docs link to have also been updated.

nlambert’s picture

I have posted a message on the forums (module development), however your comment relates to my situation exactly... don't wish to crosspost but...

Same config:

OS X 10.9.1 Mavericks
VirtualBox 4.3.6 for OS X hosts
Vagrant 1.4.3
Vagrant Berkshelf 1.3.7
Vagrant Omnibus 1.2.1

Followed the instructions:

https://drupal.org/node/2136805

On vagrant up I get:

Error executing action `install` on resource 'package[php5-cgi]'

Would love to get this working.

###############
edit: just "vagrant ssh", "sudo apt-get update", "vagrant provision"

charginghawk’s picture

There's a lot of different ways to install df, but here's the basic way, that worked for me:

All commands to be run from project directory.

git clone --branch 7.x-1.x http://git.drupal.org/project/df.git
drush make df/build-df.make docroot

At this point your file structure should look like:
~/ProjectDirectory
~/ProjectDirectory/df
~/ProjectDirectory/docroot

Run install.php: example.com/install.php

cd docroot
drush df-es dfs_wem to enable the scenario.

You can also reset a scenario using drush df-rs dfs_wem or uninstall it using drush df-us dfs_wem.

Some caveats / gotchas:

  • In my experience, scenario-enabling only works with drush, so when prompted to choose a scenario during install, select “don’t install a scenario”.
  • Beware permissions issues, chmod or chown accordingly.
  • This is resource intensive, so be sure to set PHP settings as recommended: https://www.drupal.org/node/2254929
  • It uses a lot of RAM too, so you may need more if you see "mysql database has gone away" errors.
  • You may have to install some additional software packages for drush make to work, in my case unzip.