Generate Robust Vagrant Configurations

The skill instructs the assistant to act as a Vagrant configuration expert who builds robust, scalable configurations that optimize development workflows, handle complex multi-machine setups and follow infrastructure-as-code practices.

Core configuration principles: use Vagrant API version "2", define variables and environment-specific settings clearly, structure files for maintainability and team collaboration, follow DRY principles with reusable blocks, and implement error handling and validation. For resources, size VM allocation to the workload, save disk with linked clones and shared folders, choose network topologies that fit development needs, and use provider-specific optimizations for VirtualBox, VMware and others.

The basic multi-machine pattern keeps a MACHINES hash with a web machine (192.168.56.10, 2048 MB, 2 CPUs), a db machine (192.168.56.11, 4096 MB, 2 CPUs) and a cache machine (192.168.56.12, 1024 MB, 1 CPU) on the ubuntu/focal64 box. Each machine gets a hostname, a private network address and a VirtualBox provider block, plus role-specific provisioning: web forwards ports 80 and 443 to 8080 and 8443, db forwards 5432, and each role runs its own setup script.

Provider settings cover VirtualBox (memory, CPUs, linked clones, NAT DNS host resolver and proxy, IO APIC, KVM paravirtualization), VMware Desktop (memsize, numvcpus and the vmxnet3 ethernet device) and Hyper-V (memory, CPUs and virtualization extensions).

Provisioning includes inline shell with set -euo pipefail that updates the system and installs Docker and Docker Compose, external scripts with arguments, privileged mode and colored output, and Ansible with a playbook, inventory path, extra variables and inventory groups for web servers and databases.

Networking covers multiple interfaces (an internal private network, a DHCP one and a bridged public network), port forwarding with auto_correct for conflicts, and forwarding bound to 127.0.0.1. Synced folders use NFS on macOS and Linux for speed, SMB on Windows, rsync with exclusions for .git/, node_modules/ and *.log, or a disabled default sync.

Environment-specific configuration reads a VAGRANT_ENV variable that defaults to development. Development shows the GUI with 2048 MB and NFS sync; other environments run headless with 4096 MB and no default sync.

Use it when you need a Vagrantfile for a development environment with several machines, tuned for resources, network layout and sync performance.

Use host-only networks when external access is not required, use private networks for inter-VM communication, and disable the default synced folder when it is not needed. Use linked_clone = true to save disk space, allocate CPU and memory based on host resources, configure swap for memory-constrained environments and implement lazy loading for multi-machine setups. Network performance advice adds appropriate MTU sizes and DNS resolution optimizations.

Always validate configurations with vagrant validate before deployment, keep backup strategies for VM snapshots, keep Vagrantfile changes in version control, and use environment variables and secret management for sensitive configuration data.

The output is Vagrantfile Ruby code. Debugging additions include a UART serial log setting for VirtualBox and SSH agent forwarding, X11 forwarding and keep-alive. This port forwarding block shows conflict handling and loopback binding:

config.vm.network "forwarded_port", guest: 80, host: 8080, auto_correct: true
config.vm.network "forwarded_port", guest: 443, host: 8443, protocol: "tcp"
config.vm.network "forwarded_port", guest: 3000, host_ip: "127.0.0.1", host: 3000