3 ms·
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 u
by teh_klev 13y ago
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/ http://docs.vagrantup.com/v2/why-vagrant/
- coldtea 13y ago>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) http://en.wikipedia.org/wiki/Vagrant_(software)
- teh_klev 13y agoYes, 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.
- coldtea 13y ago>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.