HashiCorp Vagrant Reviews and Ratings

Use Cases and Deployment Scope

We use Vagrant exclusively to test web development projects internally. Our development team uses our proprietary Vagrant configs and boxes which mimic our staging and production environments to quickly scaffold a web project for speedy local development and testing. Our usage targets mostly php projects which require MAMP-type environments, such as Wordpress, though we've also used Vagrant for bespoke, bundled or framework websites.

Likelihood to Recommend

I would recommend this tool to a colleague looking to create a repeatably deployable local dev environment based on their staging and production environments. I would recommend this mostly for individuals or teams requiring environments with server-side software such as php, et al. There are likely less processor-heavy and smaller tools for simpler projects.

Use Cases and Deployment Scope

In my organization, Vagrant is used to managing VMs using VirtualBox and Chef Client as the provisioner. This allows users to automatically install software, change configurations and all of the lifecycle used to deploy later on production, without any additional concerns during the process of development, since is a VM-controlled environment.

Likelihood to Recommend

Vagrant is well suited to be integrated with Chef, in order to execute configured code on one or more platforms in isolation. Associating Vagrant as a tool for building and managing virtual machine environments in a single workflow, we get an entire group of tools that are a must-have when an organization has lots of platforms that can share some configuration.

Use Cases and Deployment Scope

Vagrant is used to create virtual machines for our Drupal servers locally so we can develop on Macs and not have issues when our servers are running Linux. It helps make sure there are no errors building a slightly different package of code, which could easily happen on a Mac.

Likelihood to Recommend

Vagrant is well suited for a team that needs a VM so that only a couple engineers can worry about the environment setup and others can focus on the code. I would give it an eight, but I had a slightly easier experience with lando. Vagrant, however, is older and more widespread, so it could have more features I didn't need.

Use Cases and Deployment Scope

We use Vagrant to provision development environments for web developers.

Likelihood to Recommend

You can easily create, share and provision development environments across platforms, excepto if you are on Windows...

Use Cases and Deployment Scope

We use Vagrant across our Product Dev teams (QA, Front end/Back end Dev, IT Operations, etc) to test our code changes, debug and preview changes made. Vagrant has been a good local way for individuals to work on their code base before making any changes to our stage or production code.

Likelihood to Recommend

Vagrant is well suited for anyone technical department that does Development and needs to thoroughly test your code, see changes and preview features. Vagrant can give the ability for users to build their own test box to be able to accomplish all of this. In our experiencing the setup and tweaking to get to a workable state has been a bit of a task but now that we have it all done its a super useful tool.

Use Cases and Deployment Scope

We use Vagrant to run virtual machines for local development of our web applications. Each team across our department uses it, but with various configurations. Vagrant allows us to test our applications locally using the same operating system and software configurations as our production servers, so we are able to get a better idea of how things will work once deployed.

Likelihood to Recommend

Vagrant works well for the local development of any website or web application. It shouldn't be very difficult to set up for someone comfortable with Unix and command line usage. It's great for those wanting to get local development as close as possible to the production environment.

It's less appropriate for more design focused developers who are not super comfortable with the command line. Though once set up and configured, it's pretty easy to teach anyone how to use it.

Use Cases and Deployment Scope

I switched to vagrant from DesktopServer for my local development stack when updating to High Sierra. Vagrant is a much more versatile and robust product that gives me flexibility and automation. I use it to spin up Wordpress websites locally and give them a local domain. DesktopServer only allowed 3 instances, but with Vagrant I can use as many as I need.

Likelihood to Recommend

Vagrant is great if you are working on websites or applications locally and need to set up a container that manages the environment. I'm no longer struck with having to work only in one version of a language as well. I can debug locally with an old project in PHP 5.3 or work on a new project that uses PHP 7

Use Cases and Deployment Scope

Used by software developers to create virtual machines where the software that is being developed can be deployed, executed and tested. Also used by consultants to create test or development environments where other products that are delivered to customers can be configured and proven to work as they are needed before putting them in production environments.

Likelihood to Recommend

It saves lot of time by making new machine deployments quick and easy. Only one person has to write and upkeep the configuration files and everyone else can then use them without knowing how to modify them. All they need to do is to install Vagrant and type one command to create the machines so whole team doesn't need to be trained on how to configure Vagrant. However Vagrant creates full virtual machines so it needs a powerful host computer and it always takes a while to bring them up.

Use Cases and Deployment Scope

Vagrant provides a framework and automation tools to deploy virtual machines for local development of many sites and applications. This allows safer development and testing, and can be more efficient with the use of local resources and 0 network latency. In tandem with other tools, such as version control and deployment tools, Vagrant is a popular part of many development tool-sets.

Likelihood to Recommend

If you have a technical expert or if a pre-built box or configuration wizard can meet your needs, Vagrant is a great fit. Even an expert could find it time-consuming to start with Vagrant and related technologies from scratch, so starting from a pre-built environment is highly recommended. Finding an appropriate box will be more or less common depending on your technology stack. LAMP is common as are many Node stacks.

Use Cases and Deployment Scope

Vagrant is used for local development of websites, APIs and web applications. By being able to mimic the production server environment we're able to eliminate the potential for any compatibility issues that can occur when running the code on a different architecture than it was originally built on. It's also helpful in the reverse-- Vagrant ensures that every developer is using the exact same environment.

Likelihood to Recommend

Extremely useful, but can get a little complicated to maintain several environments. If you only work on one or a handful of sites Vagrant is awesome. If you have dozens to maintain it gets a little more cumbersome. If ensuring compatibility is a must have it's a no-brainer and excellent for sandboxing projects.