TrustRadius Insights for HashiCorp Vagrant are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Decentralized tool with flexibility: Users consistently praise Vagrant as a decentralized tool that allows them to create container packages for starting projects. This feature provides the flexibility needed to work with different styles of WordPress installs or even create custom environments, enhancing their overall development experience.
Easy configuration for local development: Reviewers appreciate Vagrant's ability to easily set ports and URLs for local development. This convenient feature enables them to seamlessly work on their projects without encountering any issues, such as SQL problems, which they may face when using other tools like MAMP or DesktopServer.
Efficiency and repeatability in development: Many users highlight the efficiency of Vagrant in scaffolding a development and test environment. They consistently achieve repeatable results, ensuring that their projects are built on a solid foundation. Additionally, this efficient workflow saves time and effort during the development process.
Loading Reviews List....
HashiCorp Vagrant Reviews
6 Reviews
Engineering
Search is temporarily unavailable. Filters are still applied.
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.
Pros
Contained development environments on VMs, but with same structure as production environments
Open-source
Huge community
Easy to set up
Cons
It was great if Vagrant consumes less resources than what consumes today
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.
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.
Pros
Speed vs other VMs
Documentation
Robust, older than many VMs
Cons
Not as fast as natively running Linux
Occasionally I've had to kill instances to start new ones
Can be more confusing to set up (especially auth) compared to native Linux
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.
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.
Pros
Automation of virtual machine management tasks
Configuration of local development environment
Documentation
Cons
Support minimal - technical expertise required
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.
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.
Pros
Server Virtualization - it's easy to recreate a server environment and automate builds for other developers.
Seamless integration between the server environment and local machine. This allows you to use your preferred editor, automation tools and other applications, but have the website run in a self-contained environment
Community
Cons
Learning curve is steep - It can be challenging for someone to set up initially. After some coaching, the basics come pretty quickly though.
Relies on external Virtual Machine applications - It would be great if Vagrant itself could run the virtual machine instead of leaning on other virtualization software. This is a small detail, but would make setup simple.
Better support for running
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.
We mostly use Vagrant for operations to develop changes that will be applied to our production infrastructure via Puppet. I've also used it for some one-off development tasks I've done where I needed a "disposable" machine to try something out on. I've also used it to provision specific versions of Windows and IE for testing.
Pros
It builds VM quickly and easily, which allows them to be treated like livestock rather than pets. They can easily be thrown away and rebuilt.
Having access to a large library of VMs (via Vagrantfiles) enables rapid testing in multiple environments.
It's free and open-source.
Cons
As Vagrant's installed base has expanded, the combinations of Vagrant versions, guest OS versions, and VM providers has exploded. As a result, sometimes a particular combination doesn't work. It can be difficult to pin down the culprit, but the community is very helpful. This isn't really a knock on Vagrant - it's inevitable given its success.
