Last updated 11 October 2016. Created on 28 January 2014.
Edited by kentr, alex.designworks, therobyouknow. Log in to edit this page.

Quick start

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 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

  • - fully configurable for PHP version, DB engine, Apache or Nginx, add-ons like Varnish & Solr, etc.
  • - usage documented on these pages
  • (more actively maintained than the apache one) - usage documented on these pages

  • (if you want solr)
  • - based on PuPHPet + Drupal 7/8 automated install

Here is a provisional list of some other known setups

Looking for support? Visit the forums, or join #drupal-support in IRC.


rmus’s picture


I am wondering if DRUPAL can run on VMWare virtualized machines. In other words, does DRUPAL support VMWare virtualization?
We are limited to using VMWare with Linux or Windows Servers, and therefore need to know if that is a possibility for the Web Servers hosting the DRUBAL instance.

If the support for VMWare is not official through, has anybody outhere tried to run DRUPAL in a VMWare virtualized enviornment?

Any comments on this topic are much appreciated.


therobyouknow’s picture

Yes it should run because VMware is "just" another platform within which a Drupal-compatible web server software stack can run.

Generally, Drupal depends on common web stack software to be able to run, known as a LAMP stack (or a WAMP or MAMP stack) which can run atop many operating systems (OS) -- and they themselves can run within the virtualisation platform (check compatibility of the particular products). The AMP bit is free open source software and stands for Apache (the web server), the M is for MySQL database software and the P is for PHP. Equivalent alternatives can be used, e.g. Apache can be swapped for NGinx (or even Microsoft IIS - but here you'd possibly need a paid license for this), MySQL for another database that Drupal is compatible with. Just as an aside, in other systems unrelated to Drupal, the P can be referring to Perl or Python, for example. The preceding L, W or M refers to the OS: Linux, Windows or Mac. Generally, Drupal can run on all three OS types - as long as the components of the AMP bit are present - AND at the correct minimum versions - for more info about these see System Requirements here:

Drupal would therefore be "unaware" of what kind of virtualisation it is running on, be it VirtualBox, VMware, "real hardware" (no virtualisation i.e. directly on the machine's hardware) or other. So yes, it should run provided you have the right software as described.

Your consideration might be if you are considering running Drupal alongside other software to interoperate with them - they themselves would have their own separate requirements.

Finally general point about virtualisation - although Drupal can run on a standard web server stack in various environments as said, what virtualisation brings in terms of benefits is that it enables one to reproduce their production live environment on their local development environment, so that they can maximise confidence that what ran well there will run in production.

therobyouknow’s picture

Yes I do recall now that in a previous workplace we were using VMWare for virtualisation upon which CentOS Linux ran within - and atop that the Apache/Mysql/PHP that Drupal used. We also used Xen virtualisation before that.

So, really, particular virtualisation is not a specific requirement for Drupal as it's a very low layer in the stack that Drupal doesn't even 'see'. It's the Apache/Mysql/PHP that is of most importance to Drupal. Obviously the *performance* of the virtualisation would impact the performance of any Drupal site though -- and anything else that needs to run on the virtualisation may have specific requirements.

jmm42’s picture

Hi rmus,

It's been sometime since this post. But, I've been working on a vagrant implementation of drupal 7, within centos 7x. It implements virtualbox. But, you can easily swap it out, to use vmware (just need the corresponding license(s), and to adjust the Vagrantfile. It is a fully functional drupal-demonstration, and only needs to be cloned, then issued the vagrant up command, from terminal, to build. Remember, like any drupal installation, you'll need the database information. This can be found within the following:

Though, for some of you: by the time you read this, it is likely I've restructured (or started) my puppet implementation, into puppet modules. So, I'd use the authenticated sql user, and the corresponding password, password (that shouldn't change). Also, this repository, implements selinux, and forwards any http requests to the ssl equivalent.

But, I have not provided any sort of stigging for this environment, since Redhat/Centos 7x has not officially provided stig guidelines. I hope this repository is beneficial to people. If not, feel free to post issues.

Thank you!