Discover innovative tools, design features, unique websites, and code structure curated by the GoWeb community.
View the resources by category or by monthly GeekOut! Compilations. Check out the latest compilation below.
< Back to
Continuous Deployment with Codeship and WP Engine
The purpose of this article is to share our approach to continuous deployment for WordPress plugins and themes on our servers at WP Engine. Continuous deployment is the automated testing and delivery of code to development and production environments. Knowing your web host’s requirements is essential to setting up a continuous delivery process. Once you know this, then you can evaluate a service and later develop a solution that meets your needs. I have implemented this for more than a dozen WordPress themes and plugins, and I believe that effort was worth the time it is saving us now.
Codeship automates the process of testing, building, and deploying code to your server, and was the first such product I found which would integrate with our web host (WP Engine). It watches a repository, clones an updated branch to a virtual machine, runs your commands on it, and then deploys the result to your servers. Services like Codeship allow us to automate our existing development and deployment workflow so that changes to the code in our Git repositories are automatically made on our servers.
It adds git user data, defines a list of remote server repositories, and installs command line modules on the virtual machine. The staging servers are listed as remote git repositories in the staging branch’s setup script, and our production servers are listed as remotes in the master branch’s script. Then it replaces the repository’s gitignore file with our .codeshipignore file and moves all files into a folder structure relative to the root directory of our servers:
Our typical build script imports Node and Bower modules and uses Grunt to compile Sass and Coffee files:
It uses the repo’s gruntfile (example) to perform a different set of tasks for the staging and production servers:
Note that we use Compass’s expanded output with sourcemaps for developing Sass files and a compressed output for production. A web browser’s inspection tool can detect sourcemaps and use them to show you where a CSS rule is located in your Sass files. This is essential for troubleshooting or modifying Sass as quickly as possible.
Once the build script has finished, the deploy script commits changes to the cloned repository and pushes them to our WP Engine servers:
If this is the first time you’re using the Git Push feature for a particular WP Engine install, you might need to use this git push command instead to avoid a “missing branch” error:
We can only send code to WP Engine servers from Codeship using their git push feature. It replaces user input authorization with an SSH key. The .codeshipignore file allows us to exclude unneeded files from the commit and reduce upload times. Since our projects are authorized git push users with the WP Engine servers we push to, the last command pushes our final commit to the remote server repositories we defined during setup.
The video tutorial demonstrates how to implement this process. What follows are the same steps I take to connect each of our repositories to our WP Engine servers using Codeship.
Using Codeship to deploy Github repos to WP Engine
- Create a new Codeship project and connect it to a Git repo URL
- On the Codeship General Project Settings page, copy the SSH public key
- On each WP Engine install you want connected, use the SSH public key to add a new Git Push developer named codeship-shortreponame.
- On the Codeship project’s Environment settings page, create a new variable named SERVERNAME_PRODUCTION and SERVERNAME_STAGING for each WP Engine install you want connected.
- On the same page, define a FOLDERNAME variable as the name of the folder your repo’s files should be placed within. Also define a DIRECTORY variable as either wp-content/plugins or wp-content/themes.
- On the Codeship project’s Deployment settings page, create one pipeline for the repo’s master branch and another for the staging branch.
- Create separate custom scripts in each pipeline for the setup, build (optional), and deploy portions of the process.
- The setup script only has a few variables that need to be changed for each project: branchname, shortreponame, firstname.lastname@example.org, and SERVERNAME_ENVIRONMENT.
- The build script contains your existing build process, such as importing NPM modules or preprocessing css and js files.
- The deploy script has no variables.
- Ensure your Git repo has a master and staging branch.
- Checkout the staging branch of your repo and add a .codeshipignore file to its root directory using this template as a guide.
- Commit the change and push it to your repository. This will trigger the Codeship build process, which you can watch on the project’s main page as it moves through each line of your custom scripts.
- Once the build has finished, it will send the code to the staging server if successful or stop on the first line that results in an error. If it is successful, it will be pushed to the server! Whether or not it is successful, you can click on any line of the script to see its output, so if it fails you can use this to troubleshoot that command.
- When your build is successful, you can merge the staging branch to the master branch on your computer and then push it to the repository. This will trigger the master pipeline, which will either deploy it to your production server or result in an error.
And that’s it! Now you have an automated deployment process integrated with your existing Git repository, and all of your servers can have the latest, tested version of your plugins and themes each time you push to it. If you found this article helpful, please leave a comment. You can view the public repositories of Agrilife Communications on Github for more information about their build processes. I can be reached by email at email@example.com.