Basically, we run a *.staging.domain.com; however, databases are always tied together. (This is for Wordpress purposes). We use [Genesis](https://github.com/genesis/) to achieve this effect.
So, do you guys work similarly to Travis-CI in that you run an instance, follow instructions in a file and how to provision and setup the site, and then instead of just running a unit test (like travis), you keep the instance running and expose it to public?
Do you use virtualization or docker instances? (Just curious!) How long do you keep them up and do you suspend the instances when it becomes disused? Will you be able to run a single instance at a time or many? (meaning, one branch at a time or will you have 20 environments setup for my 20 pull request).
In the future, will you support private repos?
Thanks! This looks REALLY badass! :)
What's the underlying technology creating the QA environment? A virtual machine? A container? How is it being configured? A CM tool?
Why are you committing before making a feature branch, is this part of some flow? (just surprised me a bit) This is as sick as automated CI gets though.
I dig the visual regression thing, though I fear combinatorial explosion for big-ish changes if it goes through the whole site or application.
