Today I’d like to announce Homebrew 2.6.0. The most significant changes since 2.5.0 are macOS Big Sur support on Intel,
brew commands replacing all
brew cask commands, the beginnings of macOS M1/Apple Silicon/ARM support and API deprecations.
To check for any issues with the Homebrew install run: brew doctor. One issue that typically comes up is an outdated or missing version of Xcode. For the latest macOS, brew doctor will warn that the Homebrew install won’t be 100% if Xcode is not up to date, so update Xcode from the App Store. To search for an application: brew search. I have uninstalled and installed Homebrew 3 times now because it seems to never allow me to install anything as it denies me permissions at the end of most installations. As an example I will post. Experienced Mac users can take advantage of Homebrew which allows them to install all kinds of tools and command lines such as htop, wget, irssi, cask, just to name a few. And if that’s something you want to do, keep reading, we are going to show you how to install Homebrew on a Mac. The installation of homebrew remains the same for the new macOS version BigSur, but we will explain how to it anyway in this article. Note for ARM processors users If your Mac uses the Apple Silicon (M1 Chip), you will have a problem with the installation till the date of publication of this article.
Major changes and deprecations since 2.5.0:
- macOS Homebrew running natively on M1/Apple Silicon/ARM has partial functionality. We recommend installing into
/opt/homebrewand forbid installing into
/usr/local(to avoid clashing with the macOS Intel install and allow their usage side-by-side). We currently recommend running Homebrew using Intel emulation with Rosetta 2.
brew tap-newwill set up GitHub Actions workflows toupload to GitHub Releases. Read the blog post for more documentation.
Other changes since 2.5.0 I’d like to highlight are the following:
- Discourse and IRC are now deprecated as official communication methods in favour of GitHub Discussions.
- Homebrew accepts donations through GitHub Sponsors and still accepts donations through Patreon. If you can afford it, please consider donating. If you’d rather not use GitHub Sponsors or Patreon (our preferred donation methods), check out the other ways to donate in our README.
Thanks to all our hard-working maintainers, contributors, sponsors and supporters for getting us this far. Enjoy using Homebrew!« back — written by Brent on November 26, 2020
Tired of managing servers? Check out Serverless Visually Explained by Matthieu Napoli and learn how to create scalable PHP applications on AWS.
# Upgrading with Homebrew
Start by making sure brew is up-to-date:
Next, upgrade PHP. You can either use the built-in php recipe, use tap
shivammathur/homebrew-php. I'd recommend the second approach, since it allows you to easily install several PHP versions and switch between them.
# Normal upgrade
# Upgrade with
To switch between versions, use the following command:
You can read more in the repository.
# Next steps
Check the current version by running
Restart Nginx or Apache:
And make sure that your local web server also uses PHP 8 by visiting this script:
The version should show
Note: if you're using Laravel Valet, please keep on reading,you need some extra steps in order for the web server to properly work.
Homebrew Mac Password
If you're using Laravel Valet, you should do the following steps to upgrade it:
You can use
valet use to switch between PHP versions:
Note that if you're using an older Valet version (prior to v2.13.18), when switching from PHP 8 to PHP 7.4 there was a bug that didn't properly update the changes. This was fixed in Valet 2.13.18 so that it now automatically removes the valet socket after having run
valet use [email protected]. If you need to do this manually, you can run:
PHP extensions are installed using pecl. I personally use Imagick, Redis and Xdebug. They can be installed like so:
You can run
pecl list to see which extensions are installed:
You can search for other extensions using
Make sure to restart your web server after installing new packages:
If you're using Laravel Valet, you should restart it as well.
Make sure all extensions are correctly installed and loaded by checking both your PHP webserver and CLI installs:
If extensions aren't properly loaded, there are two easy fixes.
First, make sure the extensions are added in the correct ini file. You can run
php --ini to know which file is loaded:
Now check the ini file:
Note that if you're testing installed extensions via the CLI, you don't need to restart nginx, apache or Valet when making changes to ini settings.
The second thing you can do, if you're updating from an older PHP version which also used pecl to install extension; is to reinstall every extension individually.
Homebrew Mac 3ds
# Last step
Uninstall Homebrew Mac
Finally you should test and upgrade your projects for PHP 8 compatibility.