macOS High Sierra, the magnificent update that killed the development environment.

[UPDATED sep 26]

macOS High Sierra is awesome, but unfortunately, it killed my “old style” development environment.

If you are still using the “old” way for development websites (a.k.a., using macOSs own apache2 and brew php), you might want to wait with upgrading to High Sierra; I don’t have a working solution yet.

PHP does not want to get installed properly

brew install homebrew/php/php71 homebrew/php/php71-xdebug --with-http24
should install PHP71 as module, but the apache tap has a fault and won’t install. The default PHP is FPM (which is preferable) installs fine but doesn’t run properly.

When I get this fixed (and I need it fixed before I can update my work computer) I will let you know :)

If you’re smart, and you’re using Local (by Flywheel), then you just fire that puppy up, you’ll get a “thank you for using Local, would you like to update” message, just click ‘Update’ and you’re done.

to be continued …


many many tests later, still no go :( So I decided to undo a few things and uninstalled all homebrew managed PHP versions. I continued to fix paths in the Apache config files and behold! IT WORKS! macOS comes with PHP 7, so for now all seems ok, but I’m not happy. It should not be hard to use a Brew version for PHP, so why doesn’t it work?

So if you already upgraded to High Sierra and need to get Apache up and running, try

for i in $(brew list | grep php); do brew uninstall $i; done
which will uninstall ANY AND ALL packages you have installed with ‘php’ in the name. If you uninstalled one too many, just re-install it :) also, if applicable,
brew uninstall httpd24

Currently, I have Apache 2.4 with PHP 7.1.7 running (Apple provided), with these apache modules enabled in addition to the default;

LoadModule php7_module libexec/apache2/
LoadModule rewrite_module libexec/apache2/
LoadModule socache_shmcb_module libexec/apache2/
LoadModule access_compat_module libexec/apache2/
LoadModule ssl_module libexec/apache2/

Hope this gets you going, maybe try an alternate method to downgrade PHP (it should still work), or be smart and start using Local (by Flywheel) ;).

Also, A former coworker suggested Laravel Valet as an alternative. It might help you, it didn’t help me. Valet uses homebrew and therefore I kept having the same issues, but, it might work for you, let me know.

again … to be continued …

Author: Remon Pel

WebDeveloper though not WebDesigner

2 thoughts on “macOS High Sierra, the magnificent update that killed the development environment.”

    1. If that works for you, go for it :) I tried all kinds of variations, the –with-http24 was an actual hint provided by a failed installation attempt.

      I’ll try it :)

Leave a Reply

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