I wonder - has anyone ever tried the approach of the entire VM binary image being the repo and doing smart bindiffs as changes? The trick would be to identify what is "code/config/program code" vs random/temp files.<p>In code tracking you do it manually by saying don't track. Here you'd need a bit more intelligence, but seems like doable.<p>And you could create then like a git for machines.<p>I may be too simplistic / not fully understand the stackrocket/blueprint/vagrant approach - but why not doing something radically simpler???
is this just vagrant (<a href="http://vagrantup.com" rel="nofollow">http://vagrantup.com</a>) as a service? How is this different/better than vagrant? Looks interesting.
When I saw StackParts this week I was reminded about how much pain is involved in getting a particular "stack part" up and running. Nice to see a potential solution.
Love the concept. Casual use of VMs-as-if-they-were-documents is a great trend that still has a lot of potential. (StackRocket/Blueprint/Vagrant/etc could possibly benefit from a Ninite-like visual interface for bootstrapping dev/server VMs.)<p>A couple landing page nits:<p>• it'd be helpful to have some extra details/screenshots for people without flash to play the demo video<p>• lots of things on the landing page seem like they should be clickable to get started, but aren't. For example, 'Create a dev stack' and 'Make a stack, customize it' button-like areas. I bet using a click-analytics heatmap you'd see a lot of stray clicks on those.
I have been having so many problems getting vagrant + chef-solo to do what I want to duplicate my rails dev env... Something simpler and more abstracted would be great. I want to spend my time coding, not configuring my environment.
It may just be me, but I tried clicking some emphasized text because it looks just like the links. E.g. I tried to click "or make your own..." in "Use our stacks, or make your own..."