Love Vagrant, so useful.
Vagrant 1.6 has been released
11–20 of 32 posts
Re: Vagrant 1.6 has been released
#12Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For examp…
I use Vagrant heavily for testing ops & puppet changes. I've actually created two screencasts on Vagrant [1] and Learning Puppet with Vagrant [2]. Basically, it allows you to quickly spin up canned VM images via CLI, and then repackage/share these for others.
[1] http://sysadmincasts.com/episodes/4-vagrant
[2] http://sysadmincasts.com/episodes/8-learning-puppet-with-vag...
Re: Vagrant 1.6 has been released
#13Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For examp…
Developing on an OS that isn't the same as your production box.
You can SSH to it, but usually you map folders between the host machine and the VM so that you use your local suite of tools on a local drive that is mapped to a location on the VM.
Re: Vagrant 1.6 has been released
#14What's new: http://www.vagrantup.com/blog/vagrant-1-6.html
Full changelog is here: https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.m...
Re: Vagrant 1.6 has been released
#15Earlier quoted context omitted.
http://docs.vagrantup.com/v2/why-vagrant/index.html has your information.
Yep, I saw that but it doesn't really answer my question. :( If you're a developer, Vagrant will isolate dependencies and their configuration within a single disposable, consistent environment, without sacrificing any of the tools you're used to working with (editors, browsers, debuggers, etc.). Once you or someone else creates a single Vagrantfile, you just need to vagrant up and everything is installed and configur…
I've tried explaining the benefits of vagrant to some of my fellow developers. I've failed every time. I've now resorted to calling it "magical" and "just try it and you'll get it".
At the very least, you can think of it as a nice CLI to the hypervisor on your machine. Something that's consistent across different host OSes - as long as you've got the right version of Vagrant :) That and synced folders is enough of a win in my books.
Edit: I noticed you are asking about workflow. That's another thing about Vagrant. I use it like a swiss army knife for various tasks as needed. It isn't really part of a workflow per say. I do a lot of exploratory programming, trying out new stacks/packages/tools, etc. It fits well with that kind of use case.
Re: Vagrant 1.6 has been released
#16While Windows guests look interesting how are people going to get the initial box? Is every individual or organization going to have to create their own box or will there be some way to get a box if you are part of MSDN?
For what it's worth, the same guy makes Packer, a tool to create your own boxes. https://github.com/mitchellh/packer
It even allows you to replace the functionality of Vagrant - in place- to create, spin up, and provision the box all in one command.
It's super awesome.
Re: Vagrant 1.6 has been released
#17While Windows guests look interesting how are people going to get the initial box? Is every individual or organization going to have to create their own box or will there be some way to get a box if you are part of MSDN?
You have to acquire an ISO in some legal way yourself. Then, you can use something like packer-windows which has pre-built templates for various versions of Windows to build Vagrant-compatible boxes in about 10 minutes: https://github.com/joefitzgerald/packer-windows
It isn't as easy as "download pre-built Linux box" but for environments that are using Windows, this workflow has been amazing for them above what they used to do, and is quite fast.
Re: Vagrant 1.6 has been released
#18http://www.vagrantup.com/blog/vagrant-1-6.html > Boxes can now be compressed with LZMA - LZMA compression can result in much smaller boxes in a lot of cases, and Vagrant can now decompress LZMA-compressed boxes. any word on how this is enabled, or does it just work? I didn't see anything in the package or box docs. thanks.
Just works. Actually, LZMA compression has always works on Linux/Mac. Vagrant 1.6 is just the first release to also support LZMA compression on Windows as well. Since it is supported on all platforms, we're able to advertise it a bit.
Re: Vagrant 1.6 has been released
#19Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For examp…
For our team at least, our vagrant box is an exact version mirror (Redis, MySQL, PHP, nginx, git...) and paths of our production servers.
We have our DevOps maintain the box so the rest of the team doesn't have to worry about it. Changes to something, tell every one to pull from git, run vagrant provision and it works.
Saves us a lot of headache in "deploying" new development environments to our team.
Re: Vagrant 1.6 has been released
#20Edit: Bit the bullet and bought myself this bundle pack from Leanpub: https://leanpub.com/b/vagrant-ansible/ - Vagrant looks like a great tool to have under my belt. Ansible also looks extremely simple compared to Chef and looks like Vagrant and Ansible compliment each other beautifully. --- I guess this a good a place as any to ask, pardon my ignorance. What part of the workflow does Vagrant solve exactly? For examp…
Vagrant makes it so that you can easily make production and local dev exactly the same (using Puppet, Chef, Salt, etc.), even when your developers use many different platforms. This solves all sorts of problems, like, something working locally but not in production, or the half day spent by each developer trying to install and correctly setup some new dependency. Vagrant can share folders between the host and the VM…
Half day? I've worked in places where this was more like 3 days.