Vagrant 1.6 has been released
vagrantup.com
Vagrant 1.6 has been released
1–10 of 32 posts
Re: Vagrant 1.6 has been released
#2While 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?
Re: Vagrant 1.6 has been released
#3What's new: http://www.vagrantup.com/blog/vagrant-1-6.html
Re: Vagrant 1.6 has been released
#4Edit: 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 example, I'm building a business-class Rails application - normally I have RVM create a gemset specifically for that application. I also have PostgreSQL and MySQL installed locally for any app that needs it.
How does Vagrant fit into this workflow, what am I missing? Also, since the 'dev box' is now a virtual machine does that mean I can only ssh into it and edit code with something like Vim? Thanks for the information.
Re: Vagrant 1.6 has been released
#5http://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.
Re: Vagrant 1.6 has been released
#6Edit: 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…
http://docs.vagrantup.com/v2/why-vagrant/index.html has your information.
Re: Vagrant 1.6 has been released
#7While 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?
perhaps the modern.ie dev vms could be boxed up
Re: Vagrant 1.6 has been released
#8Edit: 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 using whatever shared folders option that Virtualization platform you're using has.
Re: Vagrant 1.6 has been released
#9Edit: 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…
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 configured for you to work. Other members of your team create their development environments from the same configuration, so whether you're working on Linux, Mac OS X, or Windows, all your team members are running code in the same environment, against the same dependencies, all configured the same way. Say goodbye to "works on my machine" bugs.
---
It doesn't answer if I can only ssh into the box and write code there. I need more actual workflow data.
Re: Vagrant 1.6 has been released
#10Earlier 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…
As jeffasinger described, you can sync folders between your local environment and the Vagrant VM. You can edit files locally, save them, and have the changes propagated without SSH'ing into the box. [1]
[1]: http://docs.vagrantup.com/v2/synced-folders/
Edit: Adding source.