3 ms·
I've had vagrant pop up, but have yet to explore it. That said, I have many fabric scripts for setting environments up. The link has little detail (first page)
by jmspring 13y ago
I've had vagrant pop up, but have yet to explore it. That said, I have many fabric scripts for setting environments up. The link has little detail (first page) on how it would benefit me with an existing toolset.
Are there examples where vagrant compares to something like an existing fabric script?
- jsmeaton 13y agoVagrant is great if you want to share VMs with co-workers. If you're using Windows and I'm using OSX and we're working on the same project that will be deployed to an Ubuntu machine, we can each `vagrant up` our own virtual machine and they will be exactly the same. Puppet or Chef provisioning of that vagrant VM will be very similar to using fabric to fully configure everything, with the added nicety that there are a tonne of puppet and chef configs that can be reused (not so much with fabric I've found). So vagrant doesn't give you anything you don't already have if you're just configuring a VM, except maybe the networking and shared folders. But being able to share that VM, destroy it, and rebuild it is where vagrant makes a lot of sense.
- jmspring 13y agoThanks. I wish links where X will solve Y addressed related w/o digging. Sometimes mobile clients aren't the best to search for the related comparison. Btw, I find the unrelated downvote on my original comment amusing. I wish we could see those doing up/down votes.
- jsmeaton 13y agoOn my comment or yours? I haven't got enough rep to see.
- HeyImAlex 13y agoHow about testing your fabric scripts? You can have a vagrant box configured exactly like your production server and do deploys to it locally using the exact same fabric scripts (just change the requisite fabric env settings). No surprises when you deploy to production.