>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, 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.
"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.
Perhaps not, but there's this wonderful tool called Google to help find out more. Also Wikipedia: http://en.wikipedia.org/wiki/Vagrant_(software)
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.
Whether I SHOULD HAVE known about Vagrant, I'll let you decide. ;)