Tired of the localhost setup like MAMP, WAMP or XAMP? Tired of the configuration, ‘etc/hosts’, and stuff like that.
We’ve been experimenting with Laravel Valet for the last months now and decided not to go back. Its super easy, fast and reliable.
Before you start, make sure no other service is using port 80.
We’ll get started with installing Homebrew, the latest version of PHP (7.4 at this moment) and Composer
– You can update your Homebrew with “brew update” – Installing the latest version of PHP using Homebrew : “brew install php”
We’re going to install Valet globally to our machine so we’ll use the following command.
composer global require laravel/valet
Once installed we can run valet install…
Defining the working directory
We need to attach Valet to an directory where we’ll keep our projects. When navigated to the directory of your choice we can initiate this directory as the Valet directory by using the Park Command.
Once run, we can create new application projects in this directory. The directory name of the project will also be the url for Valet. So for example is I have a directory called “pizzawebsite” I can use the URL http://pizzawebsite.test it’s as easy as that…
It’s even possible to share a project with your team of client. Thanks to the valet share command a publicly accessible url will be created using Ngrok.
Only Laravel projects? No, many more.
For those of thought Laravel Valet is only for Laravel projects… Nope ! It can be used for Laravel, Lumen, October CMS, Drupal, Craft CMS, Magento, WordPress and many more.
Here’s an overview of what you could use while developing a project with Laravel. In order to create controllers, models, migrations, … we can use artisan.
Creating a Controller
php artisan make:controller MyController
When we want artisan to provide a controller with the “resource functions” (index, create, store, show, edit, update, destroy) predefined for us, we can simply add “–resource” to our command to provide these functions out of the box.
Just like the migration file that artisan provided for us when we used -m on the creation of a model, the migration file will be added to the /database/migrations folder.
Deploy the migration file(s) to the database
In order to get our migration file(s) migrated into the database, we need to tell artisan to migrate them. Like so:
php artisan migrate
Be aware that once a migration file has been migrated to the database, all changes to the file afterwards will be discarded. We’ll need to create a new migration file in order to add additional changes / migrations. In the database you can see the hierarchy of the migrations in the table migrations.
Off we go !
First of all you’ll need to install a few things. Ruby to get Sass, and NodeJs to get npm, so we can work with Grunt.
Step one: installing Grunt. If you have NodeJs installed properly you simply run: npm install -g grunt-cli
This will install Grunt globally. So you can use it wherever you want.
Now we need to create the “package.json” file there are several ways to do this. But I prefer to create a new file and input this.