From MAMP to Vagrant and back again

8 Comments

  1. R Scott LaMorte

    This is a great article and it reaffirmed by gut instinct to stick with MAMP Pro.

    However, regarding “No one ever complains about blowing up their MAMP install,” I recently needed MySQL 5.7 and in trying to update MAMP I horribly, horribly broke it and killed several databases. I won’t be trying that again; MAMP is great if you can work within the limits of MAMP.

    1. Well, shortly after writing this article I again moved on from MAMP… I’ve been using Local by Flywheel for what looks like almost a year now. Haven’t really looked back.

      Should probably write up another post about that…

  2. Glad I read the comments. :D

    1. Yeah, even 10 months later I’m still using Local for development, and still have written anything about it.

      1. R Scott LaMorte

        I’m still on MAMP locally, but increasingly unhappy with it. I had a huge issue where my local uses MySQL and my production site uses MariaDB and I found a query that produces totally different results between the two systems.

        And my new WordPress workflow (Sage 9) requires yarn, composer, and webpack, which makes it a bit more challenging to deploy.

        We’ve settled on CircleCI for the deployment path, and CircleCI uses Docker images.

        This has me curious about Docker solutions for my local Mac environment… which circles me back around to wanting to try Flywheel for my next project.

      2. It sounds like you’re way more versed in setting up dev environments than I. I like Local because I don’t have to think about it. As fun as it was learning Vagrant, I’m just happy to get work done. Good luck!

      3. R Scott LaMorte

        Ha! No, I had to pay a guy to set up CircleCi for me. =)

        But when I saw what he did — well, it’s essentially a Docker script file with instructions on how to instantiate a linux server with apache, mysql, php, composer, and some other utility apps. And then additional lines of text execute a pull from our github repo, runs composer update and yarn run build:production, and pushed the resulting theme to our live server.

        It’s about 30 lines of code all told and takes about 5 minutes to complete.

        And because it’s basically docker… that same script file with minor mods could be used to install a working copy of my whole project on any local or remote server.

        In theory, anyway. =)

  3. R Scott LaMorte

    Edit: composer install not composer update. The difference really threw me for a while.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.