export that manually multiple times a day can be a bit tedious so let's automate that. bash_profile to point to a different version. Now, what if you want to use a different version of PHP that's installed on your system? Well, you'd have to manually change your. If you insist on using zsh run this insted: echo 'export > ~/.zhrc To continue using bash as your default shell and to upgrade it to a newer version check out this awesome article. Important: This won't work if you're using the new zsh shell which came with the Catalina update because it ignores. To change the version of the PHP used by your shell you need to add it to your path by running: echo 'export > ~/.bash_profile For newer PHP versions like 7.3 it's just running: brew install PHP 7.0/5.6 that are deprecated and not officially supported by the Homebrew team you have one additional step, you need to add a tap: brew tap exolnet/homebrew-deprecatedīrew install install you install PHP with homebrew the default location should be and there should be a symbolic link to Check out my Stack Overflow response for more info on this topic. Thanks to Homebrew you can do it fairly easy. With time different projects for various reasons required different PHP versions so I had to run multiple PHP versions on my local machine. When I start out coding as my first step I like to use my local dev machine, a 2017 Macbook Pro. Maybe Homestead / Vagrant is enough? Or maybe you don't even need that and can use your local dev machine? Just because it works in the case of some big company does not mean it adds value to the mom and pop store you're working for, or the side hustle you're working on.ĭoes running and configuring Docker really add value if you're working in a small team 1-5 people or even worse if you're working alone and you're not running a distributed system? We should be adding complexity only if there is an upside to that trade-off. Facebook / Google / Some other big company is doing it, therefore, it must be a best practice and I should be doing it.It's a new shiny technology so it means it must be the next best solution (remember the SQL is dead long live NoSQL, now it's Restful is dead long live GraphQL, tomorrow it will be something else, yadda yadda yadda).I've noticed that people often add complexity to their systems and their workflow just because: I don't like adding unnecessary complexity if there is no need for that.

Php mac os