|Hacker News, Reddit, Stack Overflow Stats|
No public GitHub repository stats available
|Description||A tool for building and distributing development environments||Lightweight Linux for Docker||Hypervisor-agnostic Docker engine. Make VMs run like Containers|
|Why people like using this service||
|Companies using this service|
Vagrant is used in the creation of development virtual machines. Couple with Packer, low footprint vms can be created to work with.
played around with vagarant a few years back. got a few things to deploy but haven't had the need to touch it since.
Building development environments that closely match real world web environments, enabling more rapid and accurate testing and development.
Not blazing fast but we pick Vagrant for all our projects because the console mode without gui leads to a low consumption of ram memory making it the best way for DevOps ready environment requiring less configuration.
local working environment mirroring server configuration through ansible
Never leave home without it. All of my projects have at least 1 Vagrantfile for setting up a local development stack.
We use Vagrant for having isolated development environments so it doesn't interfere between different projects.
All of our local development setups use VirtualBox (through Vagrant) to ensure consistent and identical development setups, freeing us from worrying about configuration inconsistencies.
Our local development environment is powered by Vagrant, on which we run a Laravel Homestead box.
Vagrant allows me to ensure that anyone I'm collaborating with will be able to test my web application in the same environment. I also use Vagrant to setup VMs that I can use to refine my Capistrano recipes.
"The best way to ensure that local testing was possible was to normalize people’s dev environments. For this we chose Vagrant. This, combined with Chef, allows us to do our local dev in sandboxed Linux instances running locally via VirtualBox in a configuration as similar to production as possible. In addition to making dev environment setup much easier than it used to be, this ensures that each engineer has a consistent environment that is ready to run tests out of the box. The user SSHs into the local linux server and runs spec commands like they would on their host OS, and generally everything Just Works. Most people on our team combine this with Zeus, which allows the Rails environment to be preloaded for lightning fast (relatively speaking) test runs. Both Vagrant and Zeus have their share of issues, but in practice we’ve found them to be a huge time saver."