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

Vagrant 1.4

vagrantup.com

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Vagrant 1.4

#11

Post by johnbellone »

peter_l_downs wrote: post #7

> Work will begin on pulling the Vagrant AWS integration into the core distribution -- to start -- so that you can use Vagrant with AWS (and other providers) right after installing it and without having to juggle plugin versions. This is awesome, I can't wait. I've been waiting for this!

I am thrilled about this as well.

Most of my projects right now have had all of their Vagrant plugin dependencies, including Vagrant itself, in the Gemfile because I wanted to make sure any developer could get a workable development environment without worrying too much about Vagrant versions. On one hand I like the fact that I can install up-to-date plugins this way, but on the other hand I just want it to work out of the box.

Although I doubt we'll be able to get away from this. More likely it will cause other frustrations such as needing to override a plugin with a monkey patch, etc.

Re: Vagrant 1.4

#12

Post by mitchellh »

NDizzle wrote: post #8

I'm afraid of upgrading vagrant now like I am afraid of upgrading bootstrap. Too many things break - it's simply not worth the trouble of upgrading and finding all the gotchas scattered all over the place in my config files and code.

I started the vagrant-spec project to address this. A system like Vagrant is hard to fully unit test because there are a lot of side-effecty things that it does. In many cases, the best way to test it is to run things in a real-life scenario.

vagrant-spec includes a acceptance suite that we're going to be building up in order to test more of the features in a black box manner. It is slow to run but if we verify that things are passing before a release, we should be able to catch most daily use cases.

Vagrant 1.4 is the first release to run through vagrant-spec and while there are some early bug reports in some fringe areas of Vagrant trickling in, Vagrant seems to be a drop-in upgrade for most users. This shows that it is working, to some extent. And it'll only get better.

Of course, if you're nervous about it, it doesn't hurt to wait for a 1.4.1 or so on.

Re: Vagrant 1.4

#13

Post by kyberias »

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity".

In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

Re: Vagrant 1.4

#14

Post by stormbrew »

Probably not the right venue, but I'm a bit disappointed addressing the plugin versioning situation isn't listed as a thing for 1.5. There are plugins for managing plugins but they're really less than ideal.

I'd honestly just like to use bundler for it, since it's almost certainly better than anything anyone's likely to make to replace it, but using bundler to run vagrant is currently considered bad for some reason and outputs a frightening warning.

Re: Vagrant 1.4

#15

Post by misnome »

I like vagrant, but would love it to work with VMWare fusion, but cannot justify paying more than the cost of fusion for a vagrant plugin.

Anyone aware of an open source alternative to the official VMWare provisioner?

Re: Vagrant 1.4

#16

Post by [deleted] »

misnome wrote: post #15

I like vagrant, but would love it to work with VMWare fusion, but cannot justify paying more than the cost of fusion for a vagrant plugin. Anyone aware of an open source alternative to the official VMWare provisioner?

[deleted]

Re: Vagrant 1.4

#17

Post by cleaver »

NDizzle wrote: post #8

I'm afraid of upgrading vagrant now like I am afraid of upgrading bootstrap. Too many things break - it's simply not worth the trouble of upgrading and finding all the gotchas scattered all over the place in my config files and code.

I know what you mean... However, the upgrade process has gotten a lot more reliable lately. At least less problems for me.

Re: Vagrant 1.4

#18

Post by haberman »

WestCoastJustin wrote: post #4

For anyone who doesn't know. Vagrant acts like a wrapper around VMware, VirtualBox, or even AWS, so that you can easily automate testing. You can also share your Vagrant boxes (images) with others in an easy manner. Vagrant is one of those things, that once you start to use it, you wonder how you managed without it. I have created several screencasts about Vagrant: Learning Vagrant @ http://sysadmincasts.com/episodes…

Can you explain what Vagrant adds on top of VirtualBox? When I tried it it didn't seem that different than just using VirtualBox directly.

Re: Vagrant 1.4

#19

Post by mitchellh »

stormbrew wrote: post #14

Probably not the right venue, but I'm a bit disappointed addressing the plugin versioning situation isn't listed as a thing for 1.5. There are plugins for managing plugins but they're really less than ideal. I'd honestly just like to use bundler for it, since it's almost certainly better than anything anyone's likely to make to replace it, but using bundler to run vagrant is currently considered bad for some reason a…

Bundler doesn't work with Vagrant because Vagrant ships with its own Ruby and RubyGems and all that. So... your Bundler you're executing has a really screwed up state of the world.

Its something that certainly needs to be solved, but I think solutions needs more time to mature in my head as well as others.

Re: Vagrant 1.4

#20

Post by mitchellh »

kyberias wrote: post #13

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

This is linked in the 2nd sentence in the getting started section that is linked from one of the two biggest call-to-actions on the homepage: http://docs.vagrantup.com/v2/why-vagrant/

I'm sorry you couldn't find that!

Post reply on HN