MAMP vs VAGRANT?

So… I have been using MAMP so far during my “career”. But I see many people are using Vagrant. Which would you say is better, and why? I usually work alone on projects but moving more and more towards team projects.

So, for teams and wordpress, what is better?

1 Like

The advantage to Vagrant is that you can spin up a separate environment for every project. You can match that environment perfectly to any member of your team, on any device you’re working on at that time. All you need is the same VagrantFile. The advantage to MAMP/XAMPP/etc is that they’re simple for a simple project. Regardless of what enthusiasts claim, you can (and probably will) have issues with Vagrant development, at some point or another. The question is whether the benefits are worth it.

Personally, I have had problems with Vagrant, but I am still using it for the two projects I’m working on as a freelancer, at the moment. So for me, the pros have so far outweighed the cons.

You can probably get better detailed responses from members of our community who have used Vagrant longer than I have, and/or for more complicated projects. I’m still considering myself a bit new to it.

2 Likes

I will elaborate on this tomorrow but vagrant by itself is really quite useless for setting up local Dev environments. The power of vagrant comes with puphpet.com. Puphpet any semi competent developer to spin up boxes for development that can be as simple as a mamp install or much more complex with pecl packages and extensions at a few key strokes. I would agree that there is a learning curve the more complex the provisioning needs to be. Though I just set a cm up on a surface pro and it only took a couple hours to work out my issues. It tends to be easy to use puphpet on mac. Windows though can be painful but so is installing extensions and pecl packages on xamp… much more painful. Also many projects require ruby and node for front end development and installing those things on Windows can be gut wrenching painful even on Mac in some cases with ruby. Mamp/xamp solve a very specific problem in the most basic sense puphpet on the other hand solves not only problems which mamp solves but replicating prod environments in general that is technology agnostic. Most projects use many different technologies and typically those technologies are much easier to install locally on a true Linux environment. For example try installing some of the major search engines like solr and Sphinx on the a none Linux machine hell even ruby.

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.