Vagrant Reviews

Provision a virtual machine mimicking your production environment in minutes. Or, should you need, easily integrate with third-party plugins and perform advanced customizations.

When compared to Docker, swapping out components within your stack is a bit tedious.

There are plenty of tools out there to make provisioning a bit easier

We use Vagrant to run our local development virtual machines since it uses less resources on our hosts than Docker.

Provision a virtual machine mimicking your production environment in minutes. Or, should you need, easily integrate with third-party plugins and perform advanced customizations.

When compared to Docker, swapping out components within your stack is a bit tedious.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

Easy to manage a virtual machine and scriptigin that.

People is ignoring vagrant for docker and abandoning the support.

Check the vagrantfile to customize the settings of the environment

Install and configure a VM ready to develop automatically.

This software is a marvel of modern computing. Never before has it been so easy to develop in multiple environments on just one pc or laptop. With a simple two word command, a virtual machine is created and launched. Vagrant goes out to the cloud and retrieves the chosen OS allowing for the developer to concentrate on the project rather than wasting extra time maintaining copies of development OSs and doing manual installations. This also makes it very easy to have the same development variables on multiple machines for multiple team members.

I dislike that it is not more widely used. I also dislike How technical and complicated it looks at first glance. Vagrant is actually very simple to grasp a decent understanding rather quickly. The average user can be up and be running with Vagrant with minimal effort contrary to what a quick overview might lead to sugest.

Vagrant allows us to set up the exact same development situation for multiple remote working team members.

Vagrant makes creating Virtual Machines super easy. Vagrantfiles can be fully customized for any operating system and can integrate with provisioning software such as Chef and Ansible.

Slight learning curve but there is lots of examples and documentation

Use it. You will enjoy how simple Vagrant makes things. waste less time setting up so that you can spend more time developing.

Recreate customized virtual environments easily for anyone on the team to work on.

The ability to distribute a configured environment to a group of people for development, QA, or general consistency

The initial configuration takes a long time to get right, but once done right, it's perfect.

Use it, I'd probably get started with something like PuPHPet or chef, to build your vagrantfile.

As soon as you pick it up from those services, look into building your own vagrant files as you'll get more flexibility out of them

In most dev houses, you'll always have inconsistency issues between developer's local environments which, at one point or another which cause an issue. With Vagrant boxes, this issue is completely eliminated.

I love that everything is stored in plain text, so you can share your provisioning file and use version control software like Git.

Repackaging boxes can be very challenging and I think it should be further improved.

I use Vagrant for setting up my development environment by modifying the Vagrantfile, which can later be shared with the other members of the team. That ensure that we all use the same, or at least very similar, machine configurations.

I love that everything is stored in plain text, so you can share your provisioning file and use version control software like Git.

Repackaging boxes can be very challenging and I think it should be further improved.

What problems are you solving with the product? What benefits have you realized?

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)

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.

I am a deveopler and use vagrant in both my work and my home projects.

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)

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.

What problems are you solving with the product? What benefits have you realized?