WordPress.org

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.