N.B.

This is a fork of the repo mentioned below with some minor changes. I have just modified it so that it can be used from Bedrock's parent dir with Bedrock in a dir called site instead of the Bedrock root dir. This is useful for when being used with Trellis and your git root is one dir up.

I have also made the Sage theme optional. Set themeName="" if you are not using a Sage theme and all Sage related tasks will be ignored.

Updated 2016-08-26

---

Deploy Bedrock+Sage WordPress project to WP Engine hosting platform

Last tested: May 22, 2016

Repo: https://github.com/hello-jason/bedrock-sage-deploy-to-wpengine

Description

This bash script prepares a WordPress project built on Root's Bedrock boilerplate with the Sage starter theme and deploys it to the WP Engine hosting platform. It can be easily modified if you do not use the Sage theme.

WP Engine expects to see a standard WordPress project in the document root for your account. Since Bedrock shifts folders and files around a bit, this script temporarily moves everything back to their original locations (on a safe, temporary branch), which is then pushed to WP Engine.

The result is a properly-versioned Bedrock repo that you can safely and repeatedly deploy to WP Engine's production and staging environments.

Demo:

• Demo Bedrock+Sage site on WP Engine: http://bedrocksage.wpengine.com/
• Demo Bedrock+Sage site repo: https://github.com/hello-jason/bedrock-sage-on-wpengine-demo

Installation & Setup

1. Grab the script

Source code is available at https://github.com/hello-jason/bedrock-sage-deploy-to-wpengine. This repo is not meant to be cloned into your project. Rather, just grab the wpedeploy.sh file and place it in the top-level directory of your Bedrock project, and keep it with your project's repo.

2. Setup git push

Follow these instructions from WP Engine to setup SSH access and git push for your WP Engine account.

This readme assumes your remotes are named as follows:

• Production: wpeproduction
• Staging: wpestaging

3. Set theme variable

Out the box, this script assumes your theme's name is sage. Open wpdeploy.sh and change the following variable (around line 17).

• Set themeName to the directory name of your theme (/app/themes/yourthemename)

Usage

Run at the top level of your project, in the same directory as your .env and composer.json files. Replace each remote name with the ones you created during step 1.

Deploy to staging:

bash wpedeploy.sh wpestaging

Deploy to production:

bash wpedeploy.sh wpeproduction

FAQs

• Which branch does it deploy? - Deploys the local branch you run it on to whichever WP Engine remote you specify (production or staging)
• What about the uploads directory? - Completely ignores the uploads directory. You'll have to upload that separately via SFTP.
• How does it handle plugin versions? - You can upgrade or downgrade version numbers in the composer.json file, run composer update, then run this script to deploy the new version to WP Engine. However, this script will not delete plugins from WP Engine's servers; you will have to do that via SFTP or wp-admin.
• What about WordPress core? - This script only deploys the contents of wp-content to WP Engine's servers. You should keep WordPress core updated in your composer file, but that only benefits your local dev environment. You will manage WP core for your publicly-facing site in WP Engine's interface directly.
• Why doesn't it work on Ubuntu? - It does! But Ubuntu defaults to dash rather than bash, and the script may fail if you simply run sh. Other distros may do the same, so running this script with the bash command is important.