You may want to read our overview.

How to use this example bootstrap

Basic setup

1. Add any required additional known hosts to ssh/known_hosts - these will be appended to the known_hosts file in your vagrant box
2. Run a search and replace for site-name to whatever the wpengine site name is (site-name.wpengine.com)
3. Amend vvv-init.sh defining whether the site is a multisite or standalone
4. Remove these initial instructions, leaving the "Development environment bootstrap" heading and everything below it
5. Amend the "Development environment bootstrap" heading and paragraph below so it reflects your purpose for the particular development environment
6. Amend composer.json to reflect your project and project dependencies
7. Test everything works as expected in a VVV context

Using Composer

See Composer and Private Repos

The private and public keys are not included in this publically distributed repo, they are in the Private Repository pie/vvv, which you should be using with this vvv-init repo. You will need to add the public key to any private repos that you wish to include.

You will need to include the Composer autoload, so add this near the top of wp-config.php (which is a file you may wish to have under version control, separating out the environment specific portion into a non-version controlled wp-config-local.php):

// composer
if ( file_exists( __DIR__ . '/wp-content/vendor/autoload.php' ) ) {
	require __DIR__ . '/wp-content/vendor/autoload.php';
}

You've then got the wrapper-composer.sh and build-wpengine.sh scripts available to you.

Development environment bootstrap

This site bootstrap is designed to be used with Varying Vagrants Vagrant and a WordPress single site, running in a wp sub-directory.

To get started:

1. If you don't already have it, clone the Vagrant repo (perhaps into your ~/Vagrants/ directory, you may need to create it if it doesn't already exist)
2. Install the Vagrant hosts updater: vagrant plugin install vagrant-hostsupdater
3. Clone this branch of this repo into the www directory of your Vagrant as site-name
4. If your Vagrant is running, from the Vagrant directory run vagrant halt
5. Followed by vagrant up --provision. Perhaps a cup of tea now? The initial provisioning may take a while.

Then you can visit:

• http://local.site-name/

This script is free software, and is released under the terms of the GPL version 2 or (at your option) any later version. See license.txt.