PHPackages                             dnaber/wp-provisioner - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. dnaber/wp-provisioner

ActiveLibrary[Utility & Helpers](/categories/utility)

dnaber/wp-provisioner
=====================

Install and configure WordPress programmatic and continuable

1.0.0-alpha2(9y ago)94.2k3[10 issues](https://github.com/dnaber-de/wp-provisioner/issues)MITPHPCI failing

Since May 16Pushed 6y ago2 watchersCompare

[ Source](https://github.com/dnaber-de/wp-provisioner)[ Packagist](https://packagist.org/packages/dnaber/wp-provisioner)[ RSS](/packages/dnaber-wp-provisioner/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (4)Versions (3)Used By (0)

WP Provisioner
==============

[](#wp-provisioner)

API to instantiate and manage your WordPress installation structure. *Work in progress*

Installation
------------

[](#installation)

```
$ composer require dnaber/wp-provisioner:dev-master

```

What & why
--------------

[](#what--why)

Assuming you planning your next web project based on WordPress. The concept of this project requires 15 sites, managed by one WordPress multisite installation. Each site has its own language and a different set of settings and activated plugins and themes. You might want to set up at least a testing server and a production system. Further you have 3 colleagues working with you on this project.

Thus, you set up your local development system, create the 15 sites and make all the settings to the sites. Now you have three options to deploy these state of your system to your fellows or to the testing/production systems:

- Share database dumps. That might work for the initial setup but what happens, if the concept changes later?
- Documentation: write down every parameter of the concept and do it manually.
- Do it programmatic using WP Provisioner

How it works
------------

[](#how-it-works)

WP Provisioner is a standalone PHP commandline script that executes a set of tasks defined in a separate PHP file. Right now it provides two commands to do this.

### provision

[](#provision)

```
$ vendor/bin/wp-provisioner provision  [--file ] [--wp-dir ] [--wp_cli ]

```

This command executes the `` defined in ``. By default, the provision file is the `provision.php` in your current working directory.

Here's an example provision file that defines version `1.0.0` and installs a multisite, sets up two sites and activates two plugins:

```