In the last months at DriveK, I’ve worked a lot with WP Engine.
WP Engine, for those who don’t know, is a managed WordPress hosting company. They have worked hard on their infrastructure performance and security to give a top-notch service.
If you have a WordPress site, just create an install and forget about all those server related issues. It’s all on their side. You only have to think about your application, your themes, and your plugins.
The flip side of this is that the infrastructure is invisible. There is no concept of VPS, server, physical machine, virtual machine and such. And this means (as of January 2016), no SSH access.
That’s where deployment issues arise.
WP Engine offers two strategies for deployment: SFTP and git.
SFTP is the standard package: you connect, upload your files, delete some and stop.
Git is a bit more sophisticated, but the concept is that you have a git repository that represents your install and when you push something to this repository, it gets automatically pushed to the live site.
In DriveK, with 20+ developers working at the same time, SFTP was not an option (I would not have considered it even if I was working alone, but that’s me!).
So that left us with git.
When you’re working on a project you could have your plugins and themes in a single repository, maybe hosted on Github or Bitbucket, and then push your changes to WP Engine as well.
But when you’re working on a product with several components the situation is different. This is better explained with an example.
Mbriaco inc. is the company behind wp-cellar, a WordPress plugin that gives wine retailers a complete list of all wines, along with descriptions and data about them.
They sell this as a SaaS product, so when a wine retailer asks them for a website, they instantiate one, customizing it.
To do this, they have developed the cavatappi parent theme, containing all commonly needed features. For every wine retailer, they create a child theme.
They have chosen WP Engine as their hosting provider because they don’t want to deal with infrastructure related problems. They just want to develop wine plugins and themes!
So, recapping, they have to manage:
Being good developers, they have every component in a single git repository hosted on Github. But this doesn’t play well with WP Engine git deployment strategy.
In fact, if they were to create a single repository for every project, they would find themselves in maintenance hell.
Every repository would have the copy of the wp-cellar plugin and the cavatappi theme. And upgrading one or both would be nearly impossible.
This is the situation we found in.
As said before, we can’t abandon git, as it is the only reasonable deploy method to work with. So, for every install, we have a git repository linked with WP Engine, anyway.
What we changed, though, is the way these repositories get updated.
Instead of working directly with these repositories, we use them as the entry point for WP Engine installs.
I added an intermediate step where we update the single component, copy it to the relevant repository and then push it to WP Engine.
A diagram is worth a thousand words, so here it is:
A call to the script is something like this:
$ deploy_to installA child-theme-A
We have been using this system since last year, and it’s been working flawlessly. I even set up the script to deploy to the staging environment that WP Engine offers, and even our designers can deploy without much effort.
The only real problem resides in the setup of WP Engine git repositories. As you can read from the relevant documentation page, the procedure is long and, worst of all, nonscriptable.
So, every now and then, I have to spend nearly 2+ hours:
You can mitigate this by using a multisite so that you have to do this setup only once. But this also has its issues, as sometimes you need a separate instance.
So, this is my take on this problem. What do you think? Am I missing something? Tell me in the comments!
Do you want to work on similar problems? Come, we’re hiring!
Cover image: “Horizontal pasta press”