title: How to implement a multidev environment / workflow?
body: <p><strong>Context: switch from Pantheon</strong></p>
  
  <p>We are currently hosted with Pantheon, an opinionated platform, and we liked their <a href="https://pantheon.io/docs/pantheon-workflow/" rel="nofollow noreferrer">workflow</a> (code up from dev to live, content down from live to dev) and used it with their <a href="https://pantheon.io/docs/multidev/" rel="nofollow noreferrer">multidev</a> environments (i.e. easy cloning and pushing all around). - After 6 years they're changing their pay structure for the first time, which includes making multidev prohibitively expensive for just one site.</p>
  
  <p><strong>Usage: multidev for feature branches</strong></p>
  
  <p>We use multidev for having feature branches. For example, one might be a proposed re-design of a page - that way I can keep working in one instance without polluting the dev environment with a half built feature, while working in another to keep hammering out minor fixes and improvements and push those through to dev, qa and then live.</p>
  
  <p>Much later (when the feature branch is finally done) it gets merged with the recent version and pushed to dev, qa, and then live.</p>
  
  <p><strong>Goal: new flow</strong></p>
  
  <p>I need to either come up with a way to mimic this workflow that is easy enough that it actually gets done (manually setting up subdomains and migrating a copy of the site, etc. seems like a lot of idle work) - or replace this one with a different sane workflow.</p>
  
  <p>It's a custom WordPress site with one to a few devs working on features, plus QA, PM, etc. who need to be able to preview the feature branch before it's even allowed into the dev environment.</p>