Vagrant Cheatsheet

Top commands.

Overview

Vagrant is HashiCorp’s tool for managing reproducible development VMs. The Vagrantfile turns "works on my machine" into versioned config; the cheatsheet captures the commands operators actually use day to day.

• Vagrantfile-as-code. VM definition in Ruby; the dev environment is a file in the repo, reviewable like any other code.
• Multi-provider. VirtualBox, VMware, Hyper-V, Docker, libvirt; the same Vagrantfile works on any host platform.
• Provisioners. Shell, Ansible, Chef, Puppet; reuse existing tooling instead of writing setup from scratch.
• Snapshots plus boxes. Save/restore VM state for fast iteration; pre-built base images reduce setup time from hours to minutes.

The approach

The practical approach: Vagrantfile in the repo, provisioner-driven setup, snapshots for iteration. The team’s discipline produces consistent dev environments engineers actually want to use.

• vagrant up. Provision the VM; the canonical "give me a working environment" command.
• vagrant ssh. SSH into the VM; matches the local-first workflow most engineers prefer.
• vagrant provision. Re-run provisioners against an existing VM; supports iteration without full rebuild.
• vagrant snapshot save name. Snapshot VM state; rollback to a known-good before risky changes.
• vagrant destroy. Clean reset; the "rebuild from scratch" path that proves the Vagrantfile actually works.

Why this compounds

Vagrant mastery compounds across the team. Each Vagrantfile captures dev knowledge; team consistency grows; new engineers join with a working environment instead of a setup ticket.

• Reproducible dev environments. Vagrantfile produces identical setup; "works on my machine" stops being a debugging excuse.
• Faster onboarding. New developers run vagrant up; setup time drops from days to one command.
• Reusable provisioners. Shared provisioner code scales across projects; the team builds a library of dev primitives.
• Institutional knowledge. Each Vagrantfile teaches local infrastructure patterns; the team’s dev-environment muscle grows.

Vagrant mastery is an operational discipline that pays off across years. Nova AI Ops integrates with development telemetry, surfaces patterns, and supports the team’s local development discipline.