21–30 of 62 posts
Current features: * Landing page * Sign up form
If you're interested, sign up and shoot me an email. I'd like to learn more about what you're interested in.
Minor spelling nitpick: cnapshots -> snapshots
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.
If you want an account, please sign up at stackrocket.com and sent me an email. I'd love to chat more and see how we can make your life easier
A couple landing page nits:
• it'd be helpful to have some extra details/screenshots for people without flash to play the demo video
• 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.
is this just vagrant ( http://vagrantup.com ) as a service? How is this different/better than vagrant? Looks interesting.
In addition to Olivier's comment, we will also have deployment option to popular cloud providers such as Heroku, PHPFog and EC2
Are you doing sort of a blended app hosting/cloud offering?
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.) A couple landing page nits: • it'd be helpful to have some extra details/screenshots for people without flash to play the demo video • lots of things on the landing page seem li…
Earlier quoted context omitted.
In addition to Olivier's comment, we will also have deployment option to popular cloud providers such as Heroku, PHPFog and EC2
How will this work? It sounded like a user could just build a custom VM image and send it to you. There wouldn't be a way to deploy that to heroku, right? Are you doing sort of a blended app hosting/cloud offering?
What we have in the works is detecting if you have e.g. Redis and subscribing to that "addon" for you.
In code tracking you do it manually by saying don't track. Here you'd need a bit more intelligence, but seems like doable.
And you could create then like a git for machines.
I may be too simplistic / not fully understand the stackrocket/blueprint/vagrant approach - but why not doing something radically simpler???
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. In code tracking you do it manually by saying don't track. Here you'd need a bit more intelligence, but seems like doable. And you could create then like a git for machines. I may be too simplistic / not…
We've thought about going pure diff at the beginning and decided that to implement that method will give us less flexibility in the short term.
I speculate that do so, we would need to implement our own virtual machine (we are using virtualbox) and/or disk image format.