Documentation
Vagrant boxes
Boxes are the package format for Vagrant environments
Use case
Understand the fundamental configurations for networking and provisioning development environments.
Challenge
The cost of fixing a bug exponentially increases the closer it gets to production. Traditionally, development and production environments strive to be as close to identical as possible. However, this becomes a challenge as local environments may differ from those production environments, which tend to be much more dynamic.
Solution
Vagrant leverages a declarative configuration file to mirror production environments by providing the same operating system, packages, accounts, and configurations, all while giving users the flexibility to use their favorite editor, IDE, and browser. Vagrant also integrates with your existing configuration management tooling like Ansible, Chef, Docker, Puppet, or Salt, so you can use the same scripts to configure Vagrant as you would production.
Datadog’s monitoring solution involves hundreds of different technologies and it runs on thousands of possible stack combinations. Their solutions team is regularly challenged to build test environments that reproduce unique customer conditions and issues. Building test environments is onerous and time-consuming, but with the help of HashiCorp’s Vagrant and Terraform, they’ve developed a more scalable system with which they can build and manage test environments as a team and easily re-use each other’s work.
Documentation
Boxes are the package format for Vagrant environments
Documentation
Almost all interaction with Vagrant is done through the command-line interface
Documentation
Provisioners in Vagrant allow you to automatically install software, alter configurations, and more