DevOps for WordPress Part Two

Today is V-Day. I think my next sentence contains the most Vs in any sentence in the history of the English language.

In this post I examine Vagrant, Varying Vagrant Vagrants and Variable VVV and how they can be used to simplify development environment setup.

Yes, really, those are their real names.

Virtualisation is a key component of  DevOps for local development environments. Virtualising your dev setup provides a number of benefits including ease of replication and an increased ability to automate repetitive tasks.

These three tools, used together, provide an automated process for quickly and simply creating local virtual development environments for WordPress.

Vagrant

Vagrant is an open source software tool to create and manage local development environments. Vagrant is used in conjunction with other virtualisation software such as VirtualBox or VMware.

Varying Vagrant Vagrants

Varying Vagrant Vagrants is an open source vagrant configuration tailored for WordPress development. VVV includes required software for WordPress development including NGINX as the webserver, MariaDB for the database and PHP.

Variable VVV

Variable VVV builds on top of Varying Vagrant Vagrants to further improve and automate the setup process.

Set up a local dev environment using Variable VVV.

Install all the required software:

  1. Vagrant
  2. Varying Vagrant Vagrants
  3. Variable VVV

Once all the requirements are installed, setting up a development WordPress site is as easy as browsing to the local vagrant directory directory, in my case:

/usr/local/bin/vagrant-local/www

and typing

vv create

Variable VVV will then ask a series of questions about your WordPress install and, all things going well, set up a working WordPress development environment for you.

Image showing Variable VVV set up using terminal on a Macbook

Leave a Reply

Your email address will not be published. Required fields are marked *