I work at the command line every day. I develop in Linux, but have a Mac laptop. I use Vagrant to do all of my development.

How does that work out? On the whole pretty great. Here's what I like:

* Spinning up my development box is as simple as "vagrant up", getting in there is as simple as "vagrant ssh"

* Vagrant boxes are specified in Vagrantfiles, where you describe what steps to do when you make a new one. At this point I have codified most of what I need to spin up a new vagrant box in my Vagrant file. New computer? I'm up and running in a few minutes.

* Vagrant allows us to test out all our builds in a fully virtualized environment on developer laptops. It's actually kinda beautiful. Review collected by and hosted on G2.com.

I have only one complaint about Vagrant, and to be honest this complaint is largely related to my own misuse of the tool:

If you power off your laptop at the wrong time, it is possible for a Vagrant image to become corrupted. I lost two development boxes to this (in both cases it was when I had to hold the power button because Mac OS locked up for unrelated reasons). It sucks, but that said, it also enforces a mode of thinking around ephemeral machines that I find very helpful. Both times I've lost a vagrant dev box, I've spent some time making my Vagrantfile better so getting back to speed is increasingly painless Review collected by and hosted on G2.com.

Vagrant is much better than trying to run a production-like stack directly on your local machine, especially once you factor in complications like working with a team of developers who run different OSes. Vagrant was a game changer that revolutionized many aspects of software engineering workflow and is still a useful tool with a barrier to entry that isn't prohibitively high. Review collected by and hosted on G2.com.

It's so unbelievably slow. The rate of development is absolutely glacial. Massive bugs go unfixed and/or unreleased for several months at a time. That wouldn't be so bad if there were an easy way to switch to a development branch of the program, but there isn't. It doesn't scale as a solution: you either have to have several massive VMs installed side-by-side to keep environments discreet or you need to have to use one extra-monolithic VM that has all your environments colocated, which just moves the technical debt Vagrant was meant to solve off of your host machine and into a guest VM. Review collected by and hosted on G2.com.

It's awesome to be able to do my development locally with whatever configuration I need. I can shut it down when I'm not using it and switch between boxes quickly. Review collected by and hosted on G2.com.

There are a lot of moving pieces. Do have to decide if you're using shell scripts, puppet, ansible, chef or whatnot. I find it difficult to get it to work on local domains (http://project.app/) so I end up using a custom port which prevents me from running more than one at a time (using the same configuration). Review collected by and hosted on G2.com.

I was a developer who doesn't know the concept of DevOps. Before using Vagrant, occasionally, I was annoyed by some linux configuration, by IDE setup, by repeat LAMP stack configuration, but I had the feeling that something was wrong: there should be a better way to do it.

Until starting using Vagrant and hashicorp's other tools, such as packer, I began to know another world: DevOps.

So,

the "everything should be automatic" pattern in my brain, was developed by Linux user experience + Vagrant( hashicorp) Review collected by and hosted on G2.com.

I am currently satisfied by Vagrant and hashicor's other tools. They are good! Once you learn the "DevOps" pattern from these tools, you will be good to go for any "automatic" patterns. Review collected by and hosted on G2.com.

Some of my favorite days are spent iterating machine configurations using Vagrant. I make a change, build the VM, test it out, and destroy the VM fearlessly. It's so much better than working on real production systems or even manually building and rebuilding VMs. Review collected by and hosted on G2.com.

I have encountered some compatibility issues with ancient versions of Linux, but I was able to resolve them by stepping back a few versions of Vagrant. Given the combinatorial explosion of OSes, OS versions, virtualization tools, etc. it's a wonder there aren't more issues. Review collected by and hosted on G2.com.

I love that everything is stored in plain text, so you can share your provisioning file and use version control software like Git. Review collected by and hosted on G2.com.

Repackaging boxes can be very challenging and I think it should be further improved. Review collected by and hosted on G2.com.

Ease of getting all developers using the same environment Review collected by and hosted on G2.com.

Not easy for beginners to make changes on how a machine is setup Review collected by and hosted on G2.com.

Vagrant takes much of the guesswork out of creating new virtual machines for development, allowing for quick port and volume mapping, system provisioning, and replication. With good documentation, a great collection of prebuilt configurations, and a community that willingly provides support, Vagrant is an invaluable tool for our workflow. Review collected by and hosted on G2.com.

Vagrant sometimes hides more than it should, making it difficult for technically competent users who are new to the platform to identify where and how things are working. With a little bit of work it's possible to become familiar, but it could be easier. Review collected by and hosted on G2.com.

Vagrant allows you to have a development environment on a virtual machine that can be configured and shared with others. It allows multiple developers to work on the same environment without having to spend time configuring each machine every other time.

It helps developers to maintain the same level of configuration and all it takes are a few commands and you are good to go. Review collected by and hosted on G2.com.

Initially, it was quite difficult to get the networking right because I didn't have much experience with proxying to the virtual machine. This was a little difficult to setup so it took some time before I got used to it. Review collected by and hosted on G2.com.

it is easy to build the system to ready for everyone Review collected by and hosted on G2.com.

Right now I have no any dislike point to mention Review collected by and hosted on G2.com.