WordPress deployment with Capistrano v3

WP-Stack is a deployment tool written by Mark Jaquith and I’ve been using a slightly modified version for a while, my version was geared towards deploying plugins and themes only. Recently I updated all my Ruby gems and Capistrano was upgraded to v3, which caused WP Stack to not work anymore. I decided to created a new toolkit based on Capistrano v3.

AVH Deploy

I created a toolkit called AVH Deploy. The toolkit aims to created a set of tasks to make deployment of software, like WordPress plugins or WordPress themes more easy.
You can find the source at GitHub

Some features of the AVH Deploy toolkit:

  • AVH Deploy makes difference between production and staging deployments, and each can be configured separately.
  • Separate files for each service with its tasks, making it easy to update.
  • Some tasks are geared towards WordPress, but the toolkit is not limited to WordPress only.


AVH Deploy has some small requirements to make it work. They are basically the same as if you would run Capistrano v3 by itself.

Local system

  • Ruby >= 1.9 (JRuby and C-Ruby/YARV are supported).
  • Git

I personally recommend using rbenv to install Ruby, but choose the installation method you are comfortable with.

If you run Ubuntu, either local or on the server, consider using my Ubuntu repository for git, it’s updated with the latest version of git. Read more about it on the Git PPA for Ubuntu page.


  • You should have SSH access to the server
  • Git

Authentication setup

I could not write it better myself, so just follow the Authentication & Authorisation instructions of Capistrano itself.


We encourage you to contribute to AVH Deploy and add more tasks and.or service files to help this toolkit grow.

  • Fork AVH Deploy
  • Create a new branch named after the task.
  • Create the new task or new service file.
  • Push the branch to GitHub.
  • Create a Pull request
This article is filed under the categories Software » AVH Deploy and has no tags associated with it.