I recommend Flywheel for all my customers who are going down the WordPress route.
It's a no brainer.
When I need more control over my stack, I use DigitalOcean. It's one of the best around and it's cheap too!Find out more
I've recently started to learn Laravel and pretty early on the course introduced me to local development, by local I mean directly off the machine, rather than using a tool or VM (Homestead) as I had been doing.
The tool introduced was Valet, it's described in their documentation as 'a Laravel development environment for Mac minimalists.' Naturally, my next thought was 'if I can run a Laravel application locally, why do I need MAMP or Homestead to run WordPress sites?' - and thus I set out to see if this was possible.
Yes, it is.
Please note: A lot of what I'm about to run through I followed from this guide. I'm going to include some fixes for issues I ran into but I am in no way taking any credit for their work.
Homebrew is a package manager for MacOS, through this we can install PHP, MySQL and a whole load of other packages -you can search them all here.
Before we get to MySQL and PHP we need to actually install Homebrew. This is pretty straightforward - all we need to do is open up the Terminal and run this command
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)".
We now have Homebrew installed and can start to use this to install all the other packages we're going to need:
brew install composer
brew install php
brew install mysql
brew install wp-cli
We also need to install the package that links WP CLI and Valet together:
wp package install email@example.com:aaemnnosttv/wp-cli-valet-command.git
At this point we're going to tweak our PHP installation to expand the memory. Run
php --ini to find the config file and then nano into that file, for me this was
nano /usr/local/etc/php/7.3/conf.d/php-memory-limits.ini. Change limits to 1024M in all 3 places and then restart the service:
brew service restart mysql.
In the guide I followed they recommended to run
brew install firstname.lastname@example.org but I later had issues with this when trying to use the WP CLI tool. After an hour of so investigating I found someone else who'd ran into this issue but has found a solution. So, for this guide I'm going to recommend you install the latest version of MySQL and follow the rest of this guide to get up and running.
If you like you can follow the Laravel documentation for installing Valet as I'll just be dropping that in this guide right about… now!
composer global require laravel/valet
Once Valet is installed, try pinging any
*.test domain on your terminal using a command such as
ping foobar.test. If Valet is installed correctly you should see this domain responding on
Now we know Valet is working we need to tell it where our projects are and this is were we want to generate domains - to do this just navigate to your project folder (using the CLI), for example I'd go
/Documents/Projects/ and then you'll just need to run the
valet park command.
It was at this stage that I started to run into issues when trying to create a new site via the WP CLI tool that we installed earlier. So, prior to setting up a site lets resolve this pesky SQL 8.x issue that stops the WordPress sites from connecting.
The bug itself is due to an authentication change from
caching_sha2_password, there is much more detail about this here.
To fix it all we need to do is access MySQL by running the
mysql -uroot you'll have seen when Homebrew installed MySQL. Once we're in MySQL run the following command:
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';. What we're doing here is changing the authenticator for the
root user, I highly recommend you ONLY do this on your local environment.
Once that's done you can exit out of MySQL and we can start looking at the WP CLI installation.
Earlier on we installed the WP CLI tool via Homebrew and it's Valet package, now we've got all the other bits and bobs out of the way we can can get our WordPress site installed.
Navigate to your projects folder, once again for me this is
/Documents/Projects/, and then run
wp valet new wordpressvalet. You'll see the WP CLI tool doing it's thing and, thanks to the changes we made earlier on the SQL, we shouldn't run into any issues. Once this is complete your site will be available in the browser at https://wordpresstest.test/.
That's it, you can now spin up as many WordPress or Laravel projects as you like and run them in the browser directly from your Mac.