Hi, I'm Valerio, software engineer from Italy. To be honest, I wasn't an early adopter of local VMs as development environment (Docker, Vagrant, etc), mainly because I thought it took time to learn and I always have very limited free time. Than I discovered , the official Laravel local development environment. It has solved my doubts and simplified my life. Homestead This in no way is a replacement for referencing their documentation, and I encourage anyone who reads this to immediately read the docs after. So, with that being said, this article is for you if: You want to learn what Homestead and Vagrant are and do. You want to know why and how Homestead (or local VMs in general) will supercharge your development experience. You are expanding your business and using Xampp, MAMP, you are no longer able to recreate the production environment. I will tell you the thinking process that led me to understand what kind of benefits I had using a VM to work on my applications locally. VirtualBox + Vagrant Vagrant is a tool to automate virtual machine "setup and configuration" process. Basically to run a VM on your computer VirtualBox could be enough. But VirtualBox prepare and run just the hardware side of a VM. It's up to you to install everything you need starting from the OS. The team behind Vagrant has built a simple tool that get a script in input (called Vagrantfile) to install and configure automatically all softwares and features you want your server to have, on top of the hardware provided by VirtualBox. That’s why we need both installed on our PC. You can download and Install from here: VirtualBox https://www.virtualbox.org/wiki/Downloads You can download and install from here: Vagrant https://www.vagrantup.com/downloads.html VirtualBox + Vagrant already provide you everything you need to run the VM for your application. But at this stage you should learn more about Vagrant to manipulate the Vagrantfile and customize your server configuraiton to fit your requirements. What is Laravel Homestead Laravel Homestead is a and Vagrant setup. Thanks to Homestead I didn't need to learn anything about Vagrant. pre-packaged Vagrant Box This is simple for small teams, fit for small to medium size projects, it boots fast, and it’s enough to get anyone started with Laravel in seconds. 1. Install Homestead on your project I this, mainly because you can install it " " using Composer like any other dependencies: love per project composer require laravel/homestead --dev 2. Generate the Vagrantfile and Homstead.yaml Run the make command based on your OS: Mac / Linux: vendor/ make php bin/homestead Windows: vendor bin homestead make \\ \\ 3. Map an URL for your project The first field in the configuration file is the IP address of the VM. It could be better to have an url that map this raw IP address to reach our application with the browser. For the section, the Key references the hostname that you are calling your project. sites map Using this hostname and the IP address we’ll need to update your computer’s host file. /etc/hosts Mac: : C:\Windows\System32\drivers\etc\hosts Windows Add the entry below: 192 .168 .10 .10 demoapp .locl This is telling your computer that is located at the server IP address 192.168.10.10 (which is your VM). demoapp.locl To run multiple VM for multiple project at the same time you need to have a unique IP for each of them. You can simply increase the last IP number in the file and configure properly your computer's file: Tips! Homestead.yaml hosts 192 192 ... .168 .10 .10 demoapp .locl .168 .10 .11 another-app .locl In the Homestead.yaml file you can see: schedule: true This option provided by homestead allow us to run the server with a cron job configured to run the . This is what I mean with "I didn’t need to learn Vagrant". Laravel Task Tcheduling 4. Run the VM with your application inside In your project’s directory execute: vagrant up You will see the booting logs appear in your teminal, it takes just a few seconds, than the console back in your control. Now the VM is running in your PC and every change you make in your source code will be automatically reported inside the VM, so you can continue to work in your IDE as usual. 5. Connect with SSH You can SSH into your virtual machine by issuing the command below inside your project’s directory: vagrant ssh As you can see in this image I usually keep two terminal windows opened in my IDE (this is a screenshot of my PHPStorm): Tips! “ ” always in SSH with the project’s VM.“ ” that simply point my local terminal to the project’s directory (as by default in PHPStorm). Vagrant Local Take a time to review the homestead documentation especially “ ” to check what other softwares you can install in your server to reproduce your production environment faithfully. Installing Optional Features Conclusion Homestead provides the perfect tool to start developing with Laravel. It lets you focus on the code and not the server, but at the same time, it encouraged me into getting more familiar with the server environment. New to Inspector? Create a monitoring environment specifically designed for software developers avoiding any server or infrastructure configuration that many developers hate to deal with. Thanks to Inspector, you will never have the need to install things at the server level or make complex configuration inyour cloud infrastructure. Inspector works with a lightweight software library that you can install in your application like any other dependencies. In case of Laravel you have our official at your disposal. Developers are not always comfortable installing and configuring software at the server level, because these installations are out of the software development lifecycle, or are even managed by external teams. Laravel package Visit our website for more details: https://inspector.dev/laravel/ Previously published at https://www.inspector.dev/how-and-why-to-use-laravel-homestead-for-local-development-real-life-tips/

Keep

Make your Product Ready to Scale Using Laravel Queues

Try Inspector for free

Visit the website

Nominated for 2022 - HackerNoon Contributor of the Year - Monitoring

Nominated for Coding Guru of 2022

Nominated for 2022 - HackerNoon Contributor of the Year - Kubernetes

Nominated for 2022 - HackerNoon Contributor of the Year - Big Data

Nominated for 2022 - HackerNoon Contributor of the Year - Php

Nominated for 2022 - HackerNoon Contributor of the Year - Software Architecture

Too Long; Didn't Read

Laravel Homestead: Why, How, and When to Use It In Developement

Laravel Homestead: Why, How, and When to Use It In Developement

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

A Better Way to Monitor Your Laravel Services

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Threats to an Open API Ecosystem

10 Indications That You Should Invest in Automation Via APIs

10 Best Practices for Securing Your API

The Noonification: Getting Your API Into Production (10/28/2022)

A Better Way to Monitor Your Laravel Services

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Threats to an Open API Ecosystem

10 Indications That You Should Invest in Automation Via APIs

10 Best Practices for Securing Your API

The Noonification: Getting Your API Into Production (10/28/2022)

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps