Dev and Staging Environment Plugin provides developers with the ability to run separate Dev and Staging environments without having to manually change configuration settings both in the file system and database when migrating between environments.
Written by Matthew O’Riordan, http://mattheworiordan.com
Feedback is welcome, please branch or comment as you wish.
- Github – http://github.com/mattheworiordan/Wordpress-Plugin-Dev-and-Stage-Environment
- Home – http://mattheworiordan.com/projects/wp-plugins/dev-staging-environment
- WordPress Plugin Home – https://wordpress.org/extend/plugins/dev-and-staging-environment/
Released under the GPL License: http://www.gnu.org/licenses/gpl.html
Download the plugin in one of the following formats:
- Tar – http://mattheworiordan.com/projects/wp-plugins/dev-staging-environment/dev-staging-environment-0.2.1.tar
- Zip – http://mattheworiordan.com/projects/wp-plugins/dev-staging-environment/dev-staging-environment-0.2.1.zip
Upload the Dev and Staging Environment plugin to your blog in your PRODUCTION environment. It is imperative you install the plugin in your production environment first. Then simply activate the plugin.
Then go into the Dev & Staging Environment Options in your WordPress Admin navigation area and set your Development and Staging environment settings such as the host name which will allow the plugin to identify the Development and Staging environments, along with any database settings.
Please ensure that your web application has both read and write privileges on the wp-config.php file in the WordPress root, as well as read and write privileges to the plugin folder.
Once you have set up all your settings, you should copy the plugin files along with the wp-config.php file to your Dev and/or Staging environments, and activate the plugin.
Contributors & Developers
“Dev and Staging Environment Plugin” is open source software. The following people have contributed to this plugin.Contributors
Interested in development?
- Fixed a small bug where an empty configuration was causing a warning to be displayed in the Host field of the admin area for users with debugging on.
- Discovered that the plugin path was not guaranteed so all references to the plugin inserted into wp-config.php need to work out where the plugin has been installed.
- First release