The past month or so has given us a lot of blog posts on how, and why we should use automated build and deploy systems.
One of the best deployment systems out there (imho), is by the Ruby community, and it’s called Capistrano. We’ve been using it internally since this summer to manage and deploy our Symfony application with great success. I’ll be sharing the methodology to “Capify” a Symfony project soon, but first I wanted to share the WordPress-Capistrano project.
The goals of the project are:
- Make deployment and upgrades of WordPress easier for multiple installs of wordpress on multiple hosts
- Secure WordPress in production by setting stricter permissions, to prevent SQL/XSS attacks that modify PHP files.
- Allow one to easily manage the 3 tiered development cycle, but with WordPress
- Make deployment of WordPress simpler on the Rackspace Cloud
- Synchronization of WordPress stages (move db from production to stage, push configuration settings to production)
Currently, you can clone the repository, configure wordpress locally, setup your Capistrano recipe and start deploying.
I’ve tried to comment out the recipes, but I’m sure I need to do a better job. Feel free to ask me any questions, post issues and patches.
I’m also looking into the Moonshine project, and perhaps forking it to be independent of Rails, I’m really digging it’s ease of use and depth of features.