This project is not covered by Drupal’s security advisory policy.

The Undine project has moved to Bitbucket.

The project has been reimagined leveraging Docker instead of Vagrant, and it is strongly recommended to use the latest version of Undine available on Bitbucket. This legacy version of the project will continue to be available, though it will not be actively maintained.

Note: Undine is not a module, and does not belong in your modules directory. For more information on how to use the Vagrant-based legacy version of Undine, read on.

Undine is a cross-platform turnkey Drupal development VM based on the Acquia Cloud. The goal of the Undine project is to quickly provide a powerful, consistent environment to both new and experienced Drupalistas.

Project Status

Undine is currently in early alpha. API, set up and configuration changes may still occur at any point, though it is expected to stabilize as progress is made.

The Vagrant base box has changed for alpha6. Acquia is now using 64-bit Precise instead of Lucid, which means that environments will need to be rebuilt after updating and using `vagrant box add` to include the new base box. Note that this also means that the latest version of Undine requires a 64-bit OS (or hardware emulation support). See the relevant issue for details.

Want to help develop Undine? Download the latest development snapshot and provide feedback in the issue queue!

Why Undine?

  • Production configuration on a local install. Powered by Vagrant and Puppet, Undine combines all the advantages of a local LAMP stack with those of running on a remote server.
  • Rapid installation and configuration. Rather than spend hours setting up a development environment, Undine takes only a few minutes. This means teams can get started that much faster.
  • Consistency between developers. Setting up an environment tends to be an error-prone process. Undine standardizes environment configuration while allowing developers to use their IDE of choice. The result is the end of hearing those dreaded words: "it works on my machine."
  • Consistency between environments. Undine mimics the Acquia Cloud. Those using Acquia Cloud (or similar) will have the assurance that their sites will run as expected when deployed.

Who Can Use Undine?

Any developer or themer can start using Undine in a matter of minutes. However, those whose server configurations resemble the Acquia Cloud will reap the full benefits.

Undine also offers a means for others to explore using Vagrant and Puppet with minimal investment.


  • Single-command VM setup. Just vagrant up from the project directory and your VM is ready!
  • Easy shell access to your VM via vagrant ssh.
  • vagrant provision will revert key configuration files to defaults, allowing for safe experimentation.
  • Port forwarding to your host machine for HTTP (8080) and HTTPS (8443).
  • All aspects of the LAMP stack are pre-configured by Vagrant and Puppet. See below for specifications.
  • Shared web root allows for easy use of an IDE (./www on the host is accessible via /var/www on the VM).
  • Provides developer tools for profiling (XHProf), debugging (XDebug) and administration (Drush).

Undine VM Specifications

  • Ubuntu "Precise Pangolin" 12.04
  • Apache 2.2.14
  • PHP 5.3.27* with XDebug and XHProf
  • Percona (MySQL) Server 5.5
  • Git*
  • Drush 6.4.0

* Packages may be a couple minor versions ahead of the Acquia Cloud. This environment will be maintained to remain as closely aligned as feasible.

System Requirements

  • 64-bit host operating system
  • 1GB RAM (to be dedicated to the virtual machine)
  • VirtualBox 4.2.0
  • Vagrant 1.3.5
  • The precise64 base box supplied by Vagrant (see INSTALL.txt)


Undine and its maintainers are neither supported by nor affiliated with Acquia or any of its products or services. This is a community effort based on information made publicly available by Acquia.


Development of Undine is sponsored by Stevens Institute of Technology.

Project information

  • Module categories: Developer
  • chart icon1,357 downloads
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.