-
Notifications
You must be signed in to change notification settings - Fork 210
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5a14c8e
commit 37071c8
Showing
1 changed file
with
9 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,13 +61,14 @@ Here are a few key differences compared to the original Valet: | |
> :warning: Valet+ requires macOS and [Homebrew](https://brew.sh/). Before installation, you should make sure that no other programs such as Apache or Nginx are binding to your local machine's port 80. | ||
1. Install or update [Homebrew](https://brew.sh/) to the latest version using `brew update`. | ||
2. Install PHP 7.2 using Homebrew via `brew install [email protected]`. | ||
3. Install Composer using Homebrew via `brew install composer`. | ||
4. Install Valet+ with Composer via `composer global require weprovide/valet-plus`. | ||
5. Add `export PATH="$PATH:$HOME/.composer/vendor/bin"` to `.bash_profile` (for bash) or `.zshrc` (for zsh) depending on your shell (`echo $SHELL`) | ||
6. Run the `valet fix` command. This will check for common issues preventing Valet+ from installing. | ||
7. Run the `valet install` command. Optionally add `--with-mariadb` to use MariaDB instead of MySQL This will configure and install Valet+ and DnsMasq, and register Valet's daemon to launch when your system starts. | ||
8. Once Valet+ is installed, try pinging any `*.test` domain on your terminal using a command such as `ping -c1 foobar.test`. If Valet+ is installed correctly you should see this domain responding on `127.0.0.1`. If not you might have to restart your system. Especially when coming from the Dinghy (docker) solution. | ||
3. Add the Homebrew PHP tap for Valet+ via `henkrehorst/php`. | ||
3. Install PHP 7.2 using Homebrew via `brew install [email protected]`. | ||
4. Install Composer using Homebrew via `brew install composer`. | ||
5. Install Valet+ with Composer via `composer global require weprovide/valet-plus`. | ||
6. Add `export PATH="$PATH:$HOME/.composer/vendor/bin"` to `.bash_profile` (for bash) or `.zshrc` (for zsh) depending on your shell (`echo $SHELL`) | ||
7. Run the `valet fix` command. This will check for common issues preventing Valet+ from installing. | ||
8. Run the `valet install` command. Optionally add `--with-mariadb` to use MariaDB instead of MySQL This will configure and install Valet+ and DnsMasq, and register Valet's daemon to launch when your system starts. | ||
9. Once Valet+ is installed, try pinging any `*.test` domain on your terminal using a command such as `ping -c1 foobar.test`. If Valet+ is installed correctly you should see this domain responding on `127.0.0.1`. If not you might have to restart your system. Especially when coming from the Dinghy (docker) solution. | ||
|
||
> :information_source: Valet+ will automatically start its daemon each time your machine boots. There is no need to run `valet start` or `valet install` ever again once the initial Valet+ installation is complete. | ||
|
@@ -92,7 +93,7 @@ For example: | |
|
||
## Switching PHP version | ||
|
||
Switch PHP version using one of three commands: | ||
Switch PHP version using one of four commands: | ||
|
||
``` | ||
valet use 5.6 | ||
|