After running clean install I found that mysql could not be found. I added Mysql as below. I found this as a issue when trying to use magerun2. I get the following error:
-bash: mysql: command not found
Seems like Brew didn't add mysql to the path. I have brew setup and in my path.
brew doctor
Your system is ready to brew.
My fix was this and it worked but not sure if Mysql should have been added to path or not.
ln -sfn /usr/local/Cellar/[email protected]/5.7.22/bin/mysql /usr/local/bin/
ln -sfn /usr/local/Cellar/[email protected]/5.7.22/bin/mysqladmin /usr/local/bin/
ln -sfn /usr/local/Cellar/[email protected]/5.7.22/bin/Mysqld /usr/local/bin/
Valet+ 1.0.19
Homebrew 1.7.0-69-g7ad999f
Could you try running brew link [email protected] --force and possibly the other step mentioned in https://github.com/weprovide/valet-plus/issues/234#issuecomment-409774079? Hope that this solves your issue.
I'm having the same issue on three different machines. I first tought it was because we had some dev stuff installed before we tried Valet+ out but one of the machines was a completely new MacBook Pro without any dev stuff installed before we installed Valet+.
brew link [email protected] --force fixed it on all the machines ( thanks for that @samgranger ) but there is definitely something wrong since it's so easy to reproduce.
I have the same problem, also on a new Mac running Mojave.
Tried brew link [email protected] --force but did not work. Also got brew saying it is ready to brew.
Strange that I can access MySQL using mysql -uroot but the website I try and run say that the MySQL extension is required but if I run brew list is shows [email protected]
I have been through all of the forums and reinstalled time after time from scratch with Homebrew and valet and still the same issue... PHP server runs but cannot link to any database. I am at a complete loss :(
Any suggestions?
Dear Contributor,
With the release of Valet+ 2.0.0 the Valet+ development team and contributors have implemented the contribution guidelines. The contribution guidelines aim to improve the support and workflow of Valet+. For further information why this was implemented please check https://github.com/weprovide/valet-plus/issues/393.
We're closing this ticket because it does not follow the correct format. If you feel your ticket is still relevant we encourage you to re-open your ticket using the correct format.
Kind regards,
The Valet+ team
Most helpful comment
Could you try running
brew link [email protected] --forceand possibly the other step mentioned in https://github.com/weprovide/valet-plus/issues/234#issuecomment-409774079? Hope that this solves your issue.