PHPackages dcnl1980/valet-plus - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. dcnl1980/valet-plus ActiveLibrary dcnl1980/valet-plus =================== Blazing fast macOS PHP development environment 1.0.29(6y ago)07MITPHPPHP >=5.6 Since Jun 19Pushed 6y agoCompare [ Source](https://github.com/dcnl1980/valet-plus)[ Packagist](https://packagist.org/packages/dcnl1980/valet-plus)[ RSS](/packages/dcnl1980-valet-plus/feed)WikiDiscussions master Synced 2d ago READMEChangelogDependencies (8)Versions (73)Used By (0) [![](images/logo.png)](images/logo.png) Introduction ------------ [](#introduction) Valet+ is a development environment for macOS. No Vagrant, no Docker, no `/etc/hosts` file. ### Valet vs. Valet+ 3.0 [](#valet-vs-valet-30) This Valet Plus is working with the latest Laravel 6.x|Laravel 7.x installations. Valet+ is a third-party fork of [Laravel Valet](https://github.com/laravel/valet). Valet+ adds functionality to Valet with a goal of making things even simpler and faster. We are very grateful to the Laravel team for providing the base that we built Valet+ on. Since this is a fork we'll pull in changes from the original Valet regularly as they are released. Some of the documentation in this readme was taken from the Valet website and provided here for convenience, so that you can read this document and know about all features provided. The original documentation can be found here: . Since Valet+ is intended to replace Valet, it still uses the same `valet` command-line name. Any changes in its interface are documented below. ### Why Valet/Valet+? [](#why-valetvalet) Valet+ configures your Mac to always run Nginx in the background when your machine starts. Then, using [DnsMasq](https://en.wikipedia.org/wiki/Dnsmasq), Valet+ proxies all requests on the `*.test` domain to point to sites installed on your local machine. In other words, a blazing fast development environment. Valet+ provides a great alternative if you want flexible basics or prefer extreme speed. ### Differences from Valet [](#differences-from-valet) Here are a few key differences compared to the original Valet: - PHP version switch - Xdebug (on/off mode) - PHP extensions (mcrypt, intl, opcache) - Optimized PHP configuration using opcache - MySQL (with optimized configuration) - Redis - Elasticsearch (optional) - Many more features outlined below... Table of Contents ----------------- [](#table-of-contents) - [Introduction](#introduction) - [Installation](#installation) - [Serving sites](#serving-sites) - [Switching PHP version](#switching-php-version) - [Xdebug](#xdebug) - [PhpStorm](#phpstorm) - [Database](#database) - [Creating databases](#creating-databases) - [Importing databases](#importing-databases) - [Open database in Sequel Pro](#open-database-in-sequel-pro) - [Redis](#redis) - [Open project in browser](#open-project-in-browser) - [Securing Sites With TLS](#securing-sites-with-tls) - [Valet drivers](#valet-drivers) - [Valet Documentation](#valet-documentation) - [Credits](#credits) Installation ------------ [](#installation) > ⚠️ 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. Add the Homebrew PHP tap for Valet+ via `brew tap henkrehorst/php`. 3. Install PHP 7.4 using Homebrew via `brew install valet-php@7.4`. 4. Install Composer using Homebrew via `brew install composer`. 5. Install Valet+ with Composer via `composer global require dcnl1980/valet-plus:dev-master`. 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. > ℹ️ 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. > ℹ️ To update Valet+ to the latest version use the `composer global require dcnl1980/valet-plus:dev-master` command in your terminal. After upgrading, it is good practice to run the `valet install` command so Valet+ can make additional upgrades to your configuration files if necessary. ### Serving sites [](#serving-sites) Once Valet+ is installed, you're ready to start serving sites. Valet+ provides a command to help you serve your sites: `valet park`. Which will register the current working directory as projects root. Generally this directory is `~/sites`. 1. Create a `sites` directory: `mkdir ~/sites` 2. `cd ~/sites` 3. `valet park` That's all there is to it. Now, any project you create within your "parked" directory will automatically be served using the convention. For example: 1. `mkdir ~/sites/example` 2. `cd ~/sites/example` 3. `echo "