4 ms·
is this just vagrant (http://vagrantup.com http://vagrantup.com) as a service? How is this different/better than vagrant? Looks interesting.
by toisanji 15y ago
is this just vagrant (http://vagrantup.com http://vagrantup.com) as a service? How is this different/better than vagrant? Looks interesting.
- sayhello 15y agoYou are right. It's very similar to vagrant. When we started implementing our idea, we did not know about vagrant. The vagrant functionality is part of what we do, but we also have a hosted service and offer access control to your team. We also have a mechanism to synchronize changes between your envs
- keven 15y agoIn addition to Olivier's comment, we will also have deployment option to popular cloud providers such as Heroku, PHPFog and EC2
- themgt 15y agoHow 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?
- sayhello 15y agoWith what we have today, code on our pre-configured RoR stack will work on heroku. What we have in the works is detecting if you have e.g. Redis and subscribing to that "addon" for you.
- themgt 15y agoHave you seen the dotcloud "build files" for specifying services? I wonder if trying to encourage standardization among cloud/app hosts on a service specification file like this would be beneficial, similar to Gemfile/Procfile/etc. service 'redis', '~> 2.2.2' http://docs.dotcloud.com/guides/build-file/ http://docs.dotcloud.com/guides/build-file/