A box of tools for deploying INN's WordPress sites to WPEngine. Based on Chicago Tribune's deploy-tools.

Read documentation for all included commands here.

You'll need Python (versions 2.5 to 2.7) and pip to get started with these tools. Virtualenv and virtualenvwrapper are not required, but using them is a good practice, so we'll use them here.

Set up python dev environment:

$ sudo easy_install pip
$ sudo pip install virtualenv
$ sudo pip install virtualenvwrapper
$ echo 'source /usr/local/bin/virtualenvwrapper.sh' >> ~/.zshrc

Change "/.zshrc" to the appropriate rc file for your shell. If you're using bash: "/.bashrc".

Open a new terminal window or tab and create a virtual environment for your project:

$ mkvirtualenv projectnamegoeshere --no-site-packages
$ workon projectnamegoeshere

To use these tools, add this repo as a git submodule in the root of your project:

$ git submodule add https://github.com/INN/deploy-tools.git tools

Then pull the example files in to the root of your project:

$ cp -Rf tools/examples/* ./

Install the required libraries with pip:

Note: if you're using OS X Mavericks (10.9), you might need to set some compiler flags for Fabric and its dependencies to install correctly:

$ export CFLAGS=-Qunused-arguments
$ export CPPFLAGS=-Qunused-arguments

Then:

$ workon projectnamegoeshere
$ pip install -r requirements.txt
$ fab wp.verify_prerequisites

If your version of curl does not support sftp and you wish to use the tools in this repository to deploy, you will have to use a version of curl that does support it. For OSX users, the verification script uses brew to take care of that problem. For users of other operating systems, check your online support communities. Ubuntu users may have success in following this guide.

Now edit the example fabfile.py to adjust the settings for your project:

$ env.project_name = ''   # name for the project

You'll also need to supply the ssh environment variables for production and staging (or any other enviornments).

$ env.hosts       = []    # ssh host for production.
$ env.user        = ''    # ssh user for production.
$ env.password    = ''    # ssh password for production.

$ env.hosts       = []    # ssh host for staging.
$ env.user        = ''    # ssh user for staging.
$ env.password    = ''    # ssh password for staging.

These tools use Fabric.

To see a list of available commands:

$ fab -l

To deploy to your staging environment:

$ fab staging master deploy

And production:

$ fab production master deploy

To switch to a different branch and deploy

$ fab staging branch:newfeaturebranchname deploy

The examples directory also includes a Vagrantfile, a bunch of config files for Apache, PHP, MySQL and a boot-script.sh for provisioning a Vagrant instance for local development.

Assuming you have VirtualBox and Vagrant installed, and enough spare disk space, start the Vagrant box with:

$ vagrant up

It should take about ten minutes to complete the provisioning process, depending on your internet connection speed.

When the Vagrant box is ready, you'll want to edit your /etc/hosts file (i.e. not the hosts file on the Vagrant box), adding:

192.168.33.10 vagrant.dev

Once you've done that, you should be able to visit http://vagrant.dev and see your project running.

A couple notes:

• The Apache configuration for our Vagrant box uses the root directory of your project as the www root for vagrant.dev.
• Our provisioning script installs mysql and sets a password for the root user with value 'root'.

These tools include a few commands to ease database setup and manipulation. Read about them here.

In setting up your dev environment, you'll want to pull in all the necessary WordPress files if they are not included in the project repository. To do this, use the command:

$ fab wp.install:"3.9.1"

Where "3.9.1" identifies the tagged version of the WordPress repository that you want to use.

Fabric will download the release .zip file from Github and extract its contents to the project root.

The gitignore file included in the examples directory is a good starter for WordPress projects destined for deployment to WPEngine. It will help keep your project repo tidy by ignoring all WordPress core files that are unnecessary for deployment. Simply rename it to .gitignore to use it.