Detect Homebrew-installed PHP

[vitorgalvao]

With the removal of PHP in macOS 12, this Workflow no longer works out of the box. By using export PATH="/opt/homebrew/bin:/usr/local/bin:${PATH}" before calling php, we return that experience to people who installed PHP via Homebrew. The two paths are Homebrew’s default install locations on Apple Silicon and Intel, respectively.

[jeffbyrnes]

@vitorgalvao this isn’t necessary; Alfred was modified by its owners/maintainers to know about Homebrew-installed PHP internally. You can learn a bit more in this Oct 2021 blog post.

[vitorgalvao]

You’re misunderstanding the fix. What the Alfred update does is look for Homebrew-installed PHP in the language dropdown. So it goes from

to

But what you’re doing is calling php from inside /bin/bash. Alfred won’t modify your code and change the path to PHP there. If you’re calling the scripts from Bash or Zsh, you have to either use the full path to PHP or edit your PATH. Understanding the scripting environment goes into more detail.

The oversight in the Workflow is not hypothetical.

[jeffbyrnes]

🤦🏻‍♂️

Thanks for the patient reply, I had forgotten how this particular workflow is written.

Reopening, and I'll see if I can find some cycles this week to get this sorted!

[eduwass]

Some initial context: M1 MBP, I am running PHP from homebrew.

@jeffbyrnes for some reason when downloading the latest release file from the link in README:
https://github.com/willfarrell/alfred-pkgman-workflow/releases/latest/download/Package.Managers.alfredworkflow

... the fix that you applied here is not present (PATH in info.plist was empty).

So it threw the error mentioned here: #160

[jeffbyrnes]

@eduwass hmm. Ok, I’ll see about fixing that up.