Re:Vagrant 1.4
by eyepulp on Monday December 09, 2013 @09:49PM
(#6878699)
We're using vagrant and ansible to manage local dev instances with the same ansible scripts responsible for provisioning/deployment to our production boxes. My thought being the less I manage with vagrant, and the more I codify stuff in ansible, the more predictable things are when I go to provision/deploy in production.
I'm thrilled with how vagrant helps the process locally, but at the same time want to do as little as possible in vagrant because it's not applicable/involved when I provision/manage a box @ Linode or Digital Ocean.
Am I under-utilizing vagrant? Or missing a greater benefit by limiting its role?
I'm thrilled with how vagrant helps the process locally, but at the same time want to do as little as possible in vagrant because it's not applicable/involved when I provision/manage a box @ Linode or Digital Ocean.
Am I under-utilizing vagrant? Or missing a greater benefit by limiting its role?