Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Otto, the successor to Vagrant

hashicorp.com

Post reply on HN
Print view View original

11–20 of 185 posts

Re: Otto, the successor to Vagrant

#11

Post by ldpg »

bryanlarsen wrote: post #8

Does this use Heroku buildpacks or do they reinvent the wheel? Edit: Otto appears to do a lot of things. But the part that everybody's complaining about is the "magic" part, the part that sets up a system automatically based on the language of the app. Heroku buildpacks also perform this magic, and have been open sourced and have a large community that helps maintain them. They're useful outside of Heroku -- for inst…

In that analogy Heroku buildpacks are more like the boot the police put on your car.

Re: Otto, the successor to Vagrant

#14

Post by mrrsm »

Kiro wrote: post #10
LukeB_UK wrote: post #9

All Ruby development environments look alike, all PHP development environments look alike, etc. Did they do any user research? Doesn't feel like it based on the above statement.

What do you mean? How is the statement false?

As far as looking alike goes I think it could end with uses Ruby or uses PHP. A lot of modules will differ for different use cases. I may not need any of the modules another user needs.

Re: Otto, the successor to Vagrant

#16

Post by cleverjake »

mrrsm wrote: post #14
Kiro wrote: post #10

Earlier quoted context omitted.

What do you mean? How is the statement false?

As far as looking alike goes I think it could end with uses Ruby or uses PHP. A lot of modules will differ for different use cases. I may not need any of the modules another user needs.

nothing about mentions installing modules for you. This is about the environment, not the actual project

Re: Otto, the successor to Vagrant

#17

Post by brudgers »

LukeB_UK wrote: post #9

All Ruby development environments look alike, all PHP development environments look alike, etc. Did they do any user research? Doesn't feel like it based on the above statement.

Mitchell Hashimoto has been supporting Vagrant users for several years now. I wouldn't be surprised if that experience has led him to such a conclusion in regards to the use of Vagrant, e.g. all uses have dependency on a version of Ruby/PHP and some versions of some number of libraries and so on. The same abstractions allow control despite differences at a finer grain.

Re: Otto, the successor to Vagrant

#19

Post by tomswartz07 »

buffoon wrote: post #13

Wonder if this attempt will work properly with windows unlike packer and vagrant. Path issues, unreliable builds, ugh. This isn't the portability promise I expected.

Strange. What issues were you having?

We've been using Packer and Vagrant with Windows builds for the better part of a year now and it's been rock solid.

We actually leverage it into our Windows Deployment Server to create automatically updated OS Images to be deployed to production machines.

Re: Otto, the successor to Vagrant

#20

Post by unKlever »

LukeB_UK wrote: post #9

All Ruby development environments look alike, all PHP development environments look alike, etc. Did they do any user research? Doesn't feel like it based on the above statement.

Ruby is pretty standard and I assume PHP is as well being VERY mature. However, outside of the core things vary wildly. People using noSQL or simply using rails-api for some examples. Maybe they can manage this well and allow for variance, but Even somewhat granularly no environment is the same. I have never used Docket or containers, but this seems to be the selling point. You don't use a service to help you configure your environment, but you configure it for docker and you can run docker anywhere a bit can go.
Post reply on HN