Voting starts in March for the Drupal Association Board election.
See link to guides at footer.
Note: being reorganised and updated to cover variety of Vagrant based setups.
Why would you want this?
A Vagrant configured Virtual Machine setup for your Drupal work provides:
- Match your real go-live production environment (as opposed to a MAMP setup or putting a LAMP stack directly on your machine means your site is dependent on that environment)
- Repeatability and consistency: can re-run your scripts to setup the VM if you need to, you can share your setup with others
Pre-made Vagrant setups available
There are many. On these drupal.org pages I aim to save you time finding the best one - as several other setups may not be as maintained as frequently as the ones that I recommend.
Recommended Drupal Vagrant setups
- https://github.com/geerlingguy/drupal-vm - fully configurable for PHP version, DB engine, Apache or Nginx, add-ons like Varnish & Solr, etc.
- github.com/mikebell/drupaldev-apache - usage documented on these pages
- github.com/computerminds/parrot (if you want solr)
- github.com/alexdesignworks/drupal-dev - based on PuPHPet + Drupal 7/8 automated install
github.com/mikebell/drupaldev-nginx (more actively maintained than the apache one) - usage documented on these pages
Here is a provisional list of some other known setups
- https://drupal.org/project/vagrant (still fairly current, last release Oct 2013)
- https://drupal.org/project/quickstart (looks like it is not maintained so much these days)
- https://drupal.org/project/vdd (actively maintained, need to check whether they do a 64bit (preferred) environment as well as the 32bit)