Hacker News Reader

Comment by kyberias | Hacker News Reader

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.

View on HN

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!

Thanks for yor work Mitchell. I use Vagrant everyday.

Thanks for pointing that out. I still think it would need a concrete example or two. The text is very abstract, long sentences with multiple consecutive adjectives describing how easy it is to use and how powerful it all is. A lot of fluff really. You're trying to sell the idea, not describe how it works.

I'm SURE it's a fine tool and I'm just trying to help you communicating it better. :)

>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.

a little harsh ... but actually and unfortunately true :/

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<== environment"

All I can infer from the page is that this is a tool for building throwaway/local environments running on VM's on my desktop. But there isn't any context given on how this relates to my production environments, i.e. getting from Vagrant instance to production, there's a disconnect there for me.

[1]: http://docs.vagrantup.com/v2/why-vagrant/

>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.

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. ;)

Reply on news.ycombinator.com