This implies that the problem must be with the machine of the other person, not necessarily with the code itself. One of the biggest source of disagreements between a development team and an operations team, or even between two members of the same team, is that the code Spin-up a virtual machine to check if your code works on a clean machine How is Vagrant useful? Below are some use-cases. Here we’re basing our VM on a vagrant box called `generic/ubuntu1804` which is based on Ubuntu 18.04 operating system. Here’s an example of a minimal Vagrantfile to spin-up a VM that has NodeJS build tools pre-installed: Instead of manually installing all of the packages and tools, you can codify what you need in a configuration file called Vagrantfile, run the command vagrant up and Vagrant will boot up a fully setup VM which you can then work with using VM’s SSH( vagrant ssh) or desktop interface. a development environment you want to work with – e.g.all the applications of your choice – e.g.an operating system of your choice – e.g.With the help of code written in a declarative configuration file as long as you have Vagrant and your choice of virtualisation software installed(e.g. What this means is that you can bring up a VM that has everything you need already installed & configured in it VMWare, VirtualBox, Hyper-V, libvirt and Docker. Vagrant is an infrastructure as code(IaC) tool used to automate building and management of virtual machine(VM) environments using different providers like Vagrant enables users to create and configure lightweight, reproducible, and portable development environments. There are other IaC tools that are beneficial as well but a good amount of work can be completed using just the above four tools. There are four important Infrastructure as Code tools(or their alternatives) that every DevOps practitioner should be knowledgeable about: Vagrant, Packer, Automate management of Virtual Machines using Vagrant Introduction

Vagrant vms