There are several issues that may lead to this problem. For instance, if you are running HFS+ for Windows by Paragon Software in a BootCamp configuration, you won’t be able to see the Mac OS X system drive due to Core Storage restrictions.
![]()
Introduction
Valet is a Laravel development environment for Mac minimalists. No Vagrant, no
/etc/hosts file. You can even share your sites publicly using local tunnels. Yeah, we like it too.
Laravel Valet configures your Mac to always run Nginx in the background when your machine starts. Then, using DnsMasq, Valet proxies all requests on the
*.test domain to point to sites installed on your local machine.
In other words, a blazing fast Laravel development environment that uses roughly 7 MB of RAM. Valet isn't a complete replacement for Vagrant or Homestead, but provides a great alternative if you want flexible basics, prefer extreme speed, or are working on a machine with a limited amount of RAM.
![]()
Out of the box, Valet support includes, but is not limited to:
However, you may extend Valet with your own custom drivers.
Valet Or Homestead
As you may know, Laravel offers Homestead, another local Laravel development environment. Homestead and Valet differ in regards to their intended audience and their approach to local development. Homestead offers an entire Ubuntu virtual machine with automated Nginx configuration. Homestead is a wonderful choice if you want a fully virtualized Linux development environment or are on Windows / Linux.
Valet only supports Mac, and requires you to install PHP and a database server directly onto your local machine. This is easily achieved by using Homebrew with commands like
brew install php and brew install mysql . Valet provides a blazing fast local development environment with minimal resource consumption, so it's great for developers who only require PHP / MySQL and do not need a fully virtualized development environment.
Both Valet and Homestead are great choices for configuring your Laravel development environment. Which one you choose will depend on your personal taste and your team's needs.
Installation
Valet requires macOS and Homebrew. Before installation, you should make sure that no other programs such as Apache or Nginx are binding to your local machine's port 80.
Once Valet is installed, try pinging any
*.test domain on your terminal using a command such as ping foobar.test . If Valet is installed correctly you should see this domain responding on 127.0.0.1 .
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.
![]() Using Another Domain
By default, Valet serves your projects using the
.test TLD. If you'd like to use another domain, you can do so using the valet tld tld-name command.
For example, if you'd like to use
.app instead of .test , run valet tld app and Valet will start serving your projects at *.app automatically.
Database
If you need a database, try MySQL by running
brew install [email protected] on your command line. Once MySQL has been installed, you may start it using the brew services start [email protected] command. You can then connect to the database at 127.0.0.1 using the root username and an empty string for the password.
PHP Versions
Valet allows you to switch PHP versions using the
valet use [email protected] command. Valet will install the specified PHP version via Brew if it is not already installed:
{note} Valet only serves one PHP version at a time, even if you have multiple PHP versions installed.
Resetting Your Installation
If you are having trouble getting your Valet installation to run properly, executing the
composer global update command followed by valet install will reset your installation and can solve a variety of problems. In rare cases it may be necessary to 'hard reset' Valet by executing valet uninstall --force followed by valet install .
Upgrading
You may update your Valet installation using the
composer global update 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
Once Valet is installed, you're ready to start serving sites. Valet provides two commands to help you serve your Laravel sites:
park and link .
The
|
Command | Description |
---|---|
valet forget |
Run this command from a 'parked' directory to remove it from the parked directory list. |
valet log |
View a list of logs which are written by Valet's services. |
valet paths |
View all of your 'parked' paths. |
valet restart |
Restart the Valet daemon. |
valet start |
Start the Valet daemon. |
valet stop |
Stop the Valet daemon. |
valet trust |
Add sudoers files for Brew and Valet to allow Valet commands to be run without prompting for passwords. |
valet uninstall |
Uninstall Valet: Shows instructions for manual uninstall; or pass the --force parameter to aggressively delete all of Valet. |
Valet Directories & Files
You may find the following directory and file information helpful while troubleshooting issues with your Valet environment:
File / Path | Description |
---|---|
~/.config/valet/ |
Contains all of Valet's configuration. You may wish to maintain a backup of this folder. |
~/.config/valet/dnsmasq.d/ |
Contains DNSMasq's configuration. |
~/.config/valet/Drivers/ |
Contains custom Valet drivers. |
~/.config/valet/Extensions/ |
Contains custom Valet extensions / commands. |
~/.config/valet/Nginx/ |
Contains all Valet generated Nginx site configurations. These files are rebuilt when running the install , secure , and tld commands. |
~/.config/valet/Sites/ |
Contains all symbolic links for linked projects. |
~/.config/valet/config.json |
Valet's master configuration file |
~/.config/valet/valet.sock |
The PHP-FPM socket used by Valet's Nginx configuration. This will only exist if PHP is running properly. |
~/.config/valet/Log/fpm-php.www.log |
User log for PHP errors. |
~/.config/valet/Log/nginx-error.log |
User log for Nginx errors. |
/usr/local/var/log/php-fpm.log |
System log for PHP-FPM errors. |
/usr/local/var/log/nginx |
Contains Nginx access and error logs. |
/usr/local/etc/php/X.X/conf.d |
Contains *.ini files for various PHP configuration settings. |
/usr/local/etc/php/X.X/php-fpm.d/valet-fpm.conf |
PHP-FPM pool configuration file. |
~/.composer/vendor/laravel/valet/cli/stubs/secure.valet.conf |
The default Nginx configuration used for building site certificates. |
Powerful tool for modern apps: Apache, Nginx, MariaDB, PHP, Node.js...
-
Laragon 4.0.15
Date released: 04 Jul 2019 (8 months ago)
- Laragon 4.0.14
Date released: 26 Jun 2019 (9 months ago)
- Laragon 4.0.12
Date released: 08 Mar 2019 (one year ago)
- Laragon 4.0.11
Date released: 24 Feb 2019 (one year ago)
- Laragon 4.0.10
Date released: 14 Feb 2019 (one year ago)
- Laragon 4.0.9
Date released: 11 Feb 2019 (one year ago)
- Laragon 4.0.4
Date released: 24 Dec 2018 (one year ago)
- Laragon 4.0
Date released: 14 Nov 2018 (one year ago)
- Laragon 3.5
Date released: 18 Oct 2018 (one year ago)
- Laragon 3.4
Date released: 09 Aug 2018 (one year ago)
More Popular Software »
Join our mailing list
Stay up to date with latest software releases, news, software discounts, deals and more.
Subscribe![](/uploads/1/2/6/6/126671426/355873630.jpg)
Comments are closed.
Author
Write something about yourself. No need to be fancy, just an overview.
Archives
January 2023
December 2022
April 2020