WP-Deploy

WP Deploy is designed to solve some of the difficulties of developers working in teams using version control software and multi-server enviroments

Author:nedsbeds (profile at wordpress.org)
WordPress version required:2.0.2
WordPress version tested:3.1.4
Plugin version:0.6
Added to WordPress repository:17-01-2011
Last updated:22-04-2011
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:0
Rated by:0
Plugin URI:http://www.conditionalcomment.co.uk/wpdeploy
Total downloads:2 144
Active installs:10+
plugin download
Click to start download

WP Deploy is a plugin designed to solve some of the difficulties experienced by developers working in teams using version control software and multiple stages of deployment (local, development, staging, production etc.)

More specifically it allows multiple config files to be added through the admin system and then dynamically switched depending on the URL a user is accessing the site from.

In this way, a wordpress installation can be added to an svn repository (or any version control system) and checked out in multiple places that might have needs for differing config files.

Advanced Options and Use Cases

WPDeploy also allows you to limit certain activities for particular instances.
These activities are as follows:

  • Allow a user to use the filemanager to upload content
  • Allow a user to perform plugin installations
  • Allow a user to run the automatic WordPress upgrade

Below is an example of when one might use these capabilities.
A team of developers are working on a wordpress site together and all develop code locally, before committing to an SVN repository.
Once commited, any unit test scripts are run and then the latest version is checked out automatically to a client viewable server.
This client viewable server is where clients can produce content and will also be using the filemanager to upload images.
Since this copy of the site is automatically created, there is no developer responsible for checking this back in to the repository, any changes made to the codebase by upgrading wordpress or installing plugins won’t make it back in to the repository.
It is also desirable to keep any user generated content out of the repository
With WPDeploy, we would forbid content uploads to all machines except the version clients are creating content on, and not allow code changes on any servers that won’t get checked back in to the repository.