ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #vagrant
When a developer runs a framework that touches thousands of tiny files — think npm install, Composer dump‑autoload, or asset compilation — the default VirtualBox shared folder becomes a bottleneck.
Learn how to eliminate "it works on my machine" errors by pinning Vagrant box versions to ensure every developer uses the exact same virtual environment.
An architecture note on treating Vagrant boxes as supply-chain artifacts: the three trust boundaries (catalog, box tar, executable Vagrantfile), a minimal pinned-and-checksummed design, and the operational checks that prove it works.
Vagrant's default synced folder is slow for file-heavy work. Compare NFS, rsync, SMB, and VirtualBox shared folders by host OS, sync direction, and performance — then configure and verify NFS.
NFS synced folders improve Vagrant performance for Linux guests but create a direct host filesystem exposure. This note covers requirements, minimal Vagrantfile design, trust boundaries, checks and failure modes.
Learn how to choose between shell, Ansible, and Ansible Local provisioning in Vagrant to create idempotent, reproducible development environments across different host OSs.
Stop struggling with slow file I/O in Vagrant. Learn how to implement NFS synced folders on macOS and Linux to achieve near-native performance for your development environment.
Learn how to enable Vagrant NFS synced folders for faster host‑guest file synchronization, with a sample Vagrantfile, performance notes, and pitfalls to avoid.
Background Vagrant's retryable option for provisioners (since 2.2) re-executes a provisioner on failure, but the framework does not wrap the run in a transaction or provide an on_retry hook. This means any provisioner that writes files, modifies databases, or calls external APIs can perform the same mutations twice when a transient error triggers a retry. Co
ansible