Vagrant Reviews & Product Details

Fast setup for development environment. I'm using this to develop Laravel app. The Laravel official website provide us a Vagrant config file for us. I download the config file and run a command, then I can start to develop Laravel project, without any extra configuration needed. Very convenient!! Review collected by and hosted on G2.com.

The drawback is, it consume a lot more memory as it require to run an virtual image. I'm using MacBook Air with 4GB RAM, the machine most of the time will lag, and it's not sufficient to run 2 virtual image at same time! Review collected by and hosted on G2.com.

The fact that is just so simple and easy to use, yet it's very effective. In my previous workflow, I would just download a Linux image, set it up on VirtualBox, install everything I need for a given setup, and just then I would be able to work. With Vagrant, as easy as "vagrant up", I have all this process automated. Review collected by and hosted on G2.com.

Now that I'm used to it, I can get a Vagrant machine setup really quick. But I believe for a beginner that setup may not be so easy. Other than that, can't think of anything else I dislike. Review collected by and hosted on G2.com.

Vagrant is fantastic, it allows you to create and configure virtual development environments with popular virtualization software like Virtualbox or VMware. Review collected by and hosted on G2.com.

Vagrant is written in ruby so an update of the ruby interpret might ruin your current installation of Vagrant Review collected by and hosted on G2.com.

I really enjoy being able to sandbox my prototyping. Vagrant allows me to test things out without having to worry about dependency conflicts between separate projects. I also like that I can spin up several boxes at one time from a single file. Review collected by and hosted on G2.com.

I am not a fan of Ruby or Chef, so I rarely leverage the full power of provisioning that Vagrant offers. I also often run into networking conflicts when using Vagrant. Partially, that is because I work remotely and use VPN while using Vagrant. I also do not like the verbosity by default of standard out with the 'vagrant up' command. Review collected by and hosted on G2.com.

Vagrant is just great, i need my windows enviroment for .net and some app's that only runs in windows, and also i'm a web developer, so i need a linux enviroment, With vagrant in less than 30 mins of configuration your software is up and running, ready for all your needs, that's a great thing here, also, it's very configurable, a big advantage is that console mode without gui leads to a low consumption of ram memory, that's a big plus here, the sandbox is great in order to make proof of concept of your software, when you need to play with something you know you can break, it's your best choice, you can always delete your sandbox and no problem Review collected by and hosted on G2.com.

The fact that still requires a bit of configuration, that thing still can be improved here, i think that should be sandboxes that come with all stuff configured there, it could be a big plus. Review collected by and hosted on G2.com.

Its ease of maintaining an environment is the best thing to count with. One can have a newly installed environment at the distance of a command line, as well as destroyed and reinstalled. At the end of the day, the dev machine leaves no trace of whatever experiment we might have performed during the day, avoiding a lot of complications and risks that a common development machine might suffer from being tinkered with during a normal day of work. Review collected by and hosted on G2.com.

It takes a quite steep learning curve in order to get up and running with Vagrant solution. To make simple things as to install an operational system from scratch is as easy as pie, but to have an entire topology readily available one needs to spend quite a lot of time to make the configurations, which are nothing but pure scripts. Unless one counts with some orchestration support tools, such as Puppet or Chef, there surely is gonna be a whole lot of scripting to do in order to have a more than simple solution ready for deployment at your company. Review collected by and hosted on G2.com.

100% customizable. Easy to put into place. Lots of great recipes through google searches. Great community. Review collected by and hosted on G2.com.

Can be processor and memory intensive. Make sure you have a beefy computer. Review collected by and hosted on G2.com.

Vagrant is possibly the tool that has improved my way of working most for the last few years.

I like that it is easy to spin up a new environment, and that you can share your virtual machines with others.

Testing some new software? I do it in vagrant! Finished testing? delete the machine. No more messing around with my local system or having a bunch of software installed unnecessary.

The fact that it supports different virtualization technologies is a huge plus, for instance is use vmware fusion to provide nested virtualization to test out cloud solutions through vagrant. Review collected by and hosted on G2.com.

Sometimes a full vm is too much, docker integration would make this tool truly perfect. Review collected by and hosted on G2.com.

Vagrant is a wonderful tool for development environments. It helps me anticipate how my machine will interact with the cloud and allows me to avoid many problems before deploying the app. We have Ubuntu, CentOS, Solaris... any Linux machine wrapped in a "box." Vagrant also makes continuous delivery much easier. I've worked in a big team where each member had different OS on their local machines, and Vagrant enabled us to have a machine configured for our local setup, so any team member could work without compatibility issues or OS dependencies. Another very cool feature of Vagrant is provisions, which automate the installation of machine dependencies. Finally, Vagrant is used to build VirtualBox virtual machines, and it's Open Source. Review collected by and hosted on G2.com.

It has its learning curve, a little slow on the installation of provisions. Review collected by and hosted on G2.com.

1. The major reason why I'd use vagrant is to make sure that my development machine is almost 1-to-1 with the deployment server (hardware spec is basically too difficult to replicate in-office) this would solve issues between going from Apple's BSD to say a dependent machine which runs Ubuntu.

2. I can test vagrant scripts on remote clouds such as AWS or RackSpace with the same workflow which I followed on my local machine there is no rocket science to be learned if I am shifting from one hosting provider to other

3. As a person handling operations in my organisation Vagrant gives me a disposable environment and consistent workflow for developing and testing infrastructure management scripts. I can quickly test things like shell scripts, Chef cookbooks, Puppet modules, and more using local virtualization such as VirtualBox or VMware.

4. Personally I am working with Microsoft Azure azure provider made my life lot more easier compared to old style recycling of AWS EC2 Machines. Review collected by and hosted on G2.com.

Sometime vagrant machines are very slow for no reasons mitigating them is the best option they are many blog posts on the same try to look into them.Apart from minor errors caused due to updates I like vagrant very much.

Users with windows client will see a tough time while using this product if you need to get most out of this switch for Unix/Linux Review collected by and hosted on G2.com.