Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vagrant 2.0

hashicorp.com

Post reply on HN
Print view View original

71–80 of 120 posts

Re: Vagrant 2.0

#71

Post by epalmer »

geerlingguy wrote: post #29

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure…

I am the maintainer for a dev env for our team. We are on Mac OS X but we develop for RHEL so the vagrant image is centos. Building an image takes a few minutes but we love it.

We will probably research docker in 2018.

Re: Vagrant 2.0

#74

Post by jitl »

scrollaway wrote: post #61
jitl wrote: post #6

In the change log, I’m happy to see “improved the resilience of some Virtualbox commands.” At Airbnb, we used to use Vagrant with Virtualbox and the Chef provisioner to create our dev environments, but we migrated totally away from Vagrant after struggling with Virtualbox bugs, and strangeness with Vagrant’s internal state and locking. Seems like this issue is finally addressed: https://github.com/mitchellh/vagrant/i…

Vagrant's really falls short of its promise of "the exact same dev environment for everyone" in my experience, especially because of VirtualBox issues such as, for example, relative symlinks breaking if done in a shared folder on a mismatched guest/host OS. It's been such a source of frustration that there is no better shared folder alternative. VirtualBox is the only usable cross-platform backend, and vbox shared fo…

Shared filesystems of any sort are too slow for most application development purposes, especially if you've got a process like NPM on one of the sides trying to read and write 2.5gb of Javascript files.

We saw a 30% speedup in one of our apps by switching from NFS to two-way syncing between "native" filesystems using Unison.

See mitchellh's blog post on the subject:

http://mitchellh.com/comparing-filesystem-performance-in-vir...

Re: Vagrant 2.0

#76

Post by coolguy1982 »

geerlingguy wrote: post #29

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure…

We use Vagrant with docker containers inside running our web apps. Vagrant functions as a disposable virtual dev environment (on Mac) to do our docker development in linux and know everyone's machines are identical when developing for production. A new dev can just download our latest vagrant repo, vagrant up and it'll provision their development environment to be exactly as it should be.

It doesn't have to be one or the other.

Re: Vagrant 2.0

#77

Post by amorphid »

dmix wrote: post #58

Does anyone find Vagrant useful for personal projects? Or is it only useful for team settings?

On my Mac, I tend to use Vagrant w/ Virtualbox when I want to run Linux locally for any reason.

Re: Vagrant 2.0

#78

Post by protomikron »

apatap wrote: post #40
KZeillmann wrote: post #11

What's the use case where I'd want to use Vagrant instead of Docker?

Vagrant is also used as an easy way to spin up development environments e.g. for embedded systems via virtualbox. I am not aware of a simple way to create a GUI with docker. With vagrant it is just one line: v.gui = true

Can you elaborate on your first use case - for what kind of embedded development do you use virtualbox and how?

Regarding your second point - you can either attach a shell for testing (e.g. I often build a Dockerfile first interactively via /bin/bash inside the container) or use the hammer (a web-UI) and connect your localhost to the docker network interface.

Data exchange between host and container is also simply done via bind mounts - which might be more elaborate in production however.

Re: Vagrant 2.0

#79

Post by kevindication »

geerlingguy wrote: post #29

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure…

Just wanted to drop a note to say thanks for your nicely done ansible recipes.

Re: Vagrant 2.0

#80

Post by sslalready »

aoeuasdf1 wrote: post #66
sslalready wrote: post #59

Earlier quoted context omitted.

In practise it's much easier to just trust well-known developers by whitelisting their code-signing certificates. You could still get owned, of course, but the benefit here is that you're excluding everything not explicitly whitelisted, including drive-by downloads, crap on portable devices or random programs downloaded off the internet that someone thinks will solve their problem of the day. When people do not code-…

Does santa work with brew? If not, how do you even function?

Personally I've managaged to avoid using it so far. But yes, you can whitelist individual binaries or even directories. The lack of code-signing doesn't prevent whitelisting, it just makes your life harder than necessary.
Post reply on HN