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

51–60 of 64 posts

Re: Vagrant 1.4

#51

Post by coldtea »

teh_klev wrote: post #48
coldtea wrote: post #46

Earlier quoted context omitted.

> I've just spent 5 minutes trying to learn what Vagrant is and how it works. Well, it's 2013 and you're on HN. If you don't already know what Vagrant is, then perhaps you're not the most qualified information seeker.

Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems: "If you're a developer, Vagrant will isolate dependencies and their configuration within a single ==>disposable "If you're an operations engineer, Vagrant gives you a ==>disposable All I can infer from the page is that this…

>Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems

Perhaps not, but there's this wonderful tool called Google to help find out more. Also Wikipedia: http://en.wikipedia.org/wiki/Vagrant_(software)

Re: Vagrant 1.4

#52

Post by Wilya »

coldtea wrote: post #43
haberman wrote: post #18

Earlier quoted context omitted.

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.

What? Automatically installing VirtualBox images, and setting them up with a development environment in 2-3 commands does seem "that different than just using VirtualBox directly"?

A shell script that can spin up VirtualBox images and run puppet to provision them isn't very difficult to make and would vastly outperform vagrant.

Vagrant isn't very good as a piece of software, it's very good as a standard, because it can be used as a standard description of a development environment.

Re: Vagrant 1.4

#54

Post by AaronBBrown »

Wilya wrote: post #52
coldtea wrote: post #43

Earlier quoted context omitted.

What? Automatically installing VirtualBox images, and setting them up with a development environment in 2-3 commands does seem "that different than just using VirtualBox directly"?

A shell script that can spin up VirtualBox images and run puppet to provision them isn't very difficult to make and would vastly outperform vagrant. Vagrant isn't very good as a piece of software, it's very good as a standard, because it can be used as a standard description of a development environment.

A shell script that can spin up VirtualBox images and run puppet to provision them isn't very difficult to make

Ok. Let's see the code to do that.

Re: Vagrant 1.4

#55

Post by xwowsersx »

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…

Hey, these are great screencasts, just what I was looking for. Would be awesome to see a screencast that shows how to get an EC2 instance up and running using vagrant.

Re: Vagrant 1.4

#56

Post by peteridah »

Vagrant is an awesome tool for CI. I have used it extensively with Jenkins to provision environments, AWS deployments and Digital Ocean Servers. Recently I have used vagrant to easily manage OSX 10.8 guests on vmware-fusion, as the demand to provision environments for ios-related development is on the increase. I am not aware of any other tool that makes this easier. Vagrant RAWKS!

Re: Vagrant 1.4

#57

Post by teh_klev »

coldtea wrote: post #51
teh_klev wrote: post #48

Earlier quoted context omitted.

Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems: "If you're a developer, Vagrant will isolate dependencies and their configuration within a single ==>disposable "If you're an operations engineer, Vagrant gives you a ==>disposable All I can infer from the page is that this…

> Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems Perhaps not, but there's this wonderful tool called Google to help find out more. Also Wikipedia: http://en.wikipedia.org/wiki/Vagrant_(software)

Yes, very good, I know what Vagrant is I'm just not sure where it fits into my workflow going from dev into production. Neither the official website or that scant Wikipedia article answers my question.

Perhaps if you have enough time to patronise others you could use it more fruitfully to be constructive.

Re: Vagrant 1.4

#59

Post by kyberias »

coldtea wrote: post #46
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.

> I've just spent 5 minutes trying to learn what Vagrant is and how it works. Well, it's 2013 and you're on HN. If you don't already know what Vagrant is, then perhaps you're not the most qualified information seeker.

I didn't know what Vagrant was. Ofcourse I could have googled a bit but I decided to "test" the webpages whether they provided me the info I wanted. They kinda didn't.

Whether I SHOULD HAVE known about Vagrant, I'll let you decide. ;)

Re: Vagrant 1.4

#60

Post by coldtea »

teh_klev wrote: post #57
coldtea wrote: post #51

Earlier quoted context omitted.

> Well to be fair the "Why Vagrant?" page [1] isn't exactly clear about whether this is a tool for building throwaway environments or if it's something I should use to build out production systems Perhaps not, but there's this wonderful tool called Google to help find out more. Also Wikipedia: http://en.wikipedia.org/wiki/Vagrant_(software)

Yes, very good, I know what Vagrant is I'm just not sure where it fits into my workflow going from dev into production. Neither the official website or that scant Wikipedia article answers my question. Perhaps if you have enough time to patronise others you could use it more fruitfully to be constructive.

>Perhaps if you have enough time to patronise others you could use it more fruitfully to be constructive.

Sure, but where's the fun in that?

In any case, there's the evergreen "using X in production" Google search. Substitute X gor Vagrant and you'll be well on your way of knowing if it's a good idea or not and how to do it.

Post reply on HN