=== WP-Deploy ===
Contributors: nedsbeds
Tags: config, deployment, migration, subversion, git, svn, development teams
Requires at least: 2.0.2
Tested up to: 3.0.1
Stable tag: 

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

== Description ==

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.

== Installation ==

1. Upload the folder `wp-deploy` to the `/wp-content/plugins/` directory
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Navigate to settings -> `wp deploy settings` and start adding your server instances. Your current config will automatically be loaded in.

== Frequently Asked Questions ==

= A question that someone might have =

An answer to that question.

= What about foo bar? =

Answer to foo bar dilemma.

== Changelog ==

= 0.1 =
This is the first version of wp-deploy available.

== 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.

=== Coming Soon ===

A developer will be able to 

== A brief Markdown Example ==

Ordered list:

1. Some feature
1. Another feature
1. Something else about the plugin

Unordered list:

* something
* something else
* third thing

Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
Titles are optional, naturally.

[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
            "Markdown is what the parser uses to process much of the readme file"

Markdown uses email style notation for blockquotes and I've been told:
> Asterisks for *emphasis*. Double it up  for **strong**.

`<?php code(); // goes in backticks ?>`