Other than installing custom drivers for sub-directory type of multisite, there is no difference in setting up this type of multisite from the sub-domain type of multisite. One thing to note is that by enabling custom driver for this type of multisite, the configuration for sub-domain multisite will be overwritten and will not work. * Roots Laravel Valet and Bedrock Multisite * WordPress Multisite Subdirectory Valet Driver from Objectiv There are multiple drivers available for Valet that enable multisite with sub-directories and they provide installation instructions: Guide for the installation of the custom drivers can be found here. For this you will need to use a custom driver. Laravel Valet does not come with configuration for this setup out of the box. When you type echo $PATH, you should get something like this: Possible issues Composer not in the global system $PATH This will configure and install Valet and DnsMasq, and register Valet's daemon to launch when your system starts. Install Valet with Composer: composer global require laravel/valet. Install Laravel via Composer: composer global require laravel/installer. Be sure to restart the shell and add the ~/.composer/vendor/bin directory in your system's "PATH" (see instructions below). If you don't have Composer installed, install it via brew install composer. Install PHP using Homebrew via brew install php. Install or update Homebrew to the latest version using the brew update. It is ideal for machines with a small amount of RAM. Then, Valet proxies all requests on the *.test domain using DnsMasq to point to sites installed on your local machine. Laravel Valet configures your Mac to always run Nginx in the background when your machine starts. As stated in the official documentation, Valet is a Laravel development environment for Mac minimalists.
0 Comments
Leave a Reply. |