Based on the discussion over here: roots/roots/pull/1257.
These days your web project probably has a build step. Your build step takes your styles, scripts, and other assets and packages them for the browser. Maybe you are using gulp, grunt, or even make to orchestrate all your compilation steps. This post covers a couple methods for deploying projects with compiled assets and each method’s respective gotchas.
Source: Build Steps and Deployment
Goals: – Keep a local WordPress installation under version control (but ignore WordPress core files) – Use WP-Skeleton (wordpress core as submodule in separated folder, content and config files in root) – Use the starter theme Roots 101 – Deploy to a staging and production server (depending on the current Git branch?) – Keep uploads out of version control, sync them separately – Use a good DB migration strategy – If possible: automate repetitive tasks Read More
Following a series of videos from Amelia Briscoe to setup a workflow with wordpress and git
– Sign up to a bitbucket account
– Import Jaquith’s WordPress-Skeleton into Bitbucket
Maybe the hardest part of the WordPress workflow: deployment from a local server to a remote server.
Some ideas and tricks I found around the web.