Re:A Better Development Workflow with Vagrant
by tunesmith on Tuesday April 16, 2013 @05:50PM
(#5561147)
I'm still a bit confused - what if you are simultaneously working on two projects that each require a different version of Ruby? Do you have two different vagrant boxes lying around?
[ Parent
| on HN ]
Re:A Better Development Workflow with Vagrant
by chewxy on Tuesday April 16, 2013 @06:06PM
(#5561253)
You start off with the same baseVM (I used to use Precise32, switched to Precise64 for the first time yesterday). You specify the boxes which is based off your base VM.
From there, the path of evolution for each box will take place individually. If you have a Vagrantfile that specify for one project to use Ruby2.0beta and another Vagrantfile for another project to use Ruby1.9, you essentially have two boxes, two execution environments, but you still code on the same machine.
Re:A Better Development Workflow with Vagrant
by taylorlapeyre on Tuesday April 16, 2013 @07:51PM
(#5561688)
User chewxy explained it well, but even more simply I just have two different versions of Ruby on my development box. 1.9.3 and 2.0.0.
Re:A Better Development Workflow with Vagrant
by awongh on Wednesday April 17, 2013 @07:48AM
(#5563864)
if nothing else is different, then you can still use rvm inside the VM. If they are different environments (one is a colo rack and one is an AWS instance) then you would want 2 vagrant boxes to more closely duplicate each environment.