DEV Community: waziri ally amiri

How to Use Laravel Blade Templating Engine with a Pure Vanilla PHP Project?

waziri ally amiri — Wed, 17 Jul 2024 17:47:28 +0000

Today, I challenged myself to implement a Laravel MVC (Model, View, Controller) approach using pure vanilla PHP. To tackle this, I utilized the standard Laravel Blade templating engine for the view part of the project, but without installing Laravel since my project is purely vanilla PHP. Here’s how I achieved this integration;

I started by installing a package called Blade by JensSegers using the following Composer command:

composer require jenssegers/blade

This package allows the Blade templating engine to be used as a standalone package, making it compatible with any PHP project, not just Laravel.

Next, I ran the following command to update the illuminate/view dependency of the package to version 11.7.0, as the package does not work correctly with versions below 11.7.0:

composer require illuminate/view:11.7.0

Then, I created a database called "pdotest" with a table called "post," which has columns "name" and "body." I populated this table with data ('this is post name from database displayed using Blade template engine', 'this is post body from database displayed using Blade template engine') respectively and connected to it by creating Database.php file in root of my project and put following code:

<?php 


class Database {

    private $host = "localhost";
    private $database ="pdotest";
    private $username = "root" ;
    private $password =  '';

public function connect(){
    try {

        $conn = new PDO("mysql:host=$this->host;dbname=$this->database",$this->username,$this->password);

        // $conn->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
        // $conn = $conn->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);


        return $conn;

    } catch (PDOException $e) {

        echo "Connection failed: " . $e->getMessage();

    }
}

}


?>

Next, I created a directory called "Models" for all database manipulations. Inside this directory, I created a file named Post.php to handle operations on the "post" table. Within this file, I defined a method called post to retrieve a post by its ID, as shown below:

<?php 
require './Database.php';

class Post {

   public $conn;

   private $table="post";

   public function __construct() {
    $this->conn = (new Database)->connect(); // Access directly (less secure)
}


public function getPost($id){

    $stmt= "SELECT * FROM $this->table WHERE id = :id";

    $stmt =  $this->conn->prepare($stmt);

    $stmt->bindParam(':id', $id, PDO::PARAM_INT);

    $stmt->execute();

    return $result = $stmt->fetch();

}


}


?>

Next, I created index.php to act as a router, connecting my controller, view, and model. Inside it, I imported all my views and cache paths, which I will create for placing my Blade views and cache files. These paths were then passed to the Blade class, which comes with the Blade package we installed at the beginning. I then passed this Blade instance to the PostController class, which I will create, and called the post method of that class to get a post by its ID in the future.

<?php
require __DIR__ . '/vendor/autoload.php';
use Jenssegers\Blade\Blade;
require 'Controllers/ControllerPost.php';

$views = __DIR__ . '/views';

$cache = __DIR__ . '/cache';

if (!is_dir($cache)) {
    mkdir($cache, 0755, true);
}

$blade = new Blade($views, $cache);

// Simulate routing (In a real application, use a routing library)
$controller = new PostController($blade);

$controller->post();

?>

Then, I created a "controllers" directory at the root of my project. Inside it, I received the Blade variable from index.php (the router), called the getPost method of the Post model to get a post by its ID, and passed that post to a Blade view called "homepage."

<?php 
require 'Models/Post.php';


class PostController{

  protected $blade;

    public function __construct($blade) {
        $this->blade = $blade;
    }

  public function post(){

    $post = (new Post)->getPost(1);

    echo $this->blade->render('homepage', ['post' => $post]);


  }

}




?>

Then, I created a directory called "views" and a file named homepage.blade.php at the root of the project. Inside this file, I simply displayed the name of the post passed from the PostController, as shown below:


<h1>{{$post['name']}}</h1>

Finally, I created a "cache" directory in the root of my project to store Blade cache files, which helps to improve the performance of my project.

Now, when you visit http://localhost/laravel-blade-without-laravel/index.php in your browser, you will see the name of the post displayed as "this is post name from database displayed using Blade template engine."

Thank you for following along with this post on using the Laravel Blade templating engine in a pure vanilla PHP project. I hope it helps you in your development journey. My name is Waziri Ally Amiri, a web developer from Moshi, Tanzania. I specialize in working with Laravel and love to help others get started with this powerful framework. Feel free to reach out if you have any questions or need further assistance.

Why you should never use the date validation rule without the data_format rule in Laravel

waziri ally amiri — Fri, 10 Nov 2023 11:45:16 +0000

Hellow fellow Artisan,

The date validation rule in Laravel checks that a field is a valid date. However, it does not specify the format of the date. This can lead to errors if the user enters the date in a different format than expected.

Example if user enter incorrect date like this 20000-02-20 where instead of four digits(2000) for year five digit(200000) set , this will cause your application to break with this error below.

To avoid your application from break , you should avoid using only date rule like
'item.date_of_birth' => 'required|date|before:' .today()->subYears(7)->format('Y-m-d')
but you must use it with date_format() rule like this

'item.date_of_birth' => 'required|date|date_format:Y-m-d|before:' .today()->subYears(7)->format('Y-m-d')
so that instead of your application to break, user will get the validation error.

Happy Coding !

About the Author
Hi there, I'm a Full Stack Developer based in Tanzania with a passion for Laravel, Livewire, VueJs, TailwandCss, and web development. As a freelancer, I'm always ready to take on exciting projects and collaborate on remote work related to Laravel.

If you're looking for a dedicated Laravel developer who can help you bring your web application to life or enhance your existing Laravel project, feel free to reach out to me. I'm eager to work with you to create robust and innovative solutions for your business needs.

You can contact me at [wazirially1994@gmail.com] or connect with me at [https://github.com/WAZIRI123] and WhatsApp via:[+255653039317].

Let's turn your Laravel project into a success story together!

How to use multiple checkboxes in Livewire3

waziri ally amiri — Fri, 10 Nov 2023 10:58:38 +0000

Livewire is a powerful framework for building dynamic web applications. One of its features is the ability to easily bind checkboxes to Livewire properties. This allows you to create multiple checkbox inputs that are all bound to the same Livewire property, and the value of the property will be updated whenever any of the checkboxes are checked or unchecked.

To use multiple checkboxes in Livewire version three, you can use the following steps:

Create a public property in your Livewire component to store the values of the checkboxes. For example:

public $classes = [];

In your Blade view, loop through the checkbox options and generate a checkbox input for each option. Be sure to set the wire:model attribute of the checkbox inputs to the name of your Livewire property. For example:

@foreach ($classes as $c )
    <x-tall-crud-checkbox class="ml-2" wire:model="classes" value="{{$c->id}}" /> {{$c->name}}
@endforeach

the value of public $class propery now will be the array contain array of class ids that user checked like this

$class=[ 0 => 1 1 => 2 ]

so you can now do whatever you want with those array in your component.

Happy Coding!

You can contact me at [wazirially1994@gmail.com] or connect with me at [https://github.com/WAZIRI123] and WhatsApp via:[+255653039317].

Let's turn your Laravel project into a success story together!

Empowering Your Laravel Application with Custom Validation Rules

waziri ally amiri — Wed, 08 Nov 2023 07:58:19 +0000

Hello, fellow Artisan!
Laravel's validation system is known for its comprehensive set of built-in rules that ensure data integrity and user input correctness. However, there are cases where these built-in rules might not cover your specific validation requirements. This is where custom validation rules step in, allowing you to tailor the validation process to your unique needs.

Creating Custom Validation Rules
To define a custom validation rule in Laravel, you'll need to use a special Laravel Artisan command called php artisan make:rule. Let's illustrate this with an example. Suppose you have an attribute called start_date in your Laravel validation attributes, and you want to ensure that this date is either today or in the future, but not in the past. Since Laravel doesn't provide a built-in rule for this, you can create a custom validation rule.

To create your custom rule, run the following Artisan command:

php artisan make:rule StartDateBeforeToday

This command generates a Laravel class named StartDateBeforeToday, which extends the ValidationRule interface and includes a validate method. Here's what the class might look like:

namespace App\Rules;

use Carbon\Carbon;
use Closure;
use Illuminate\Contracts\Validation\Rule;

class StartDateBeforeToday implements Rule
{
    public function validate($attribute, $value, $fail)
    {
        if (!(Carbon::parse($value)->isToday() || Carbon::parse($value)->isFuture())) {
            $fail('The :attribute must be a date that is today or in the future.');
        }
    }
}

Inside the validate method, you can implement your custom validation logic. In this case, we're using the Carbon library to check if the date is today or in the future. If the validation fails, we call $fail with the error message we want to display to the user.

Using Your Custom Validation Rule
Now that you've created your custom validation rule, you can use it in your Laravel application. Here's an example of how to incorporate the StartDateBeforeToday rule into your validation logic:

$this->validate([
    'item.name' => ['required', 'string', 'max:255'],
    'item.slug' => [
        'required', 'string', 'max:255',
        Rule::unique('exams', 'slug')->ignore($this->exam->id)->whereNull('deleted_at')
    ],
    'item.description' => ['nullable', 'string'],
    'item.start_date' => ['required', 'date', new StartDateBeforeToday],
    'item.end_date' => ['required', 'date', 'after_or_equal:item.start_date'],
]);

In the validation array, you can see how we apply the StartDateBeforeToday rule to the item.start_date attribute. Laravel will automatically invoke your custom validation rule when validating the data, ensuring that the start_date is either today or in the future.

Custom validation rules empower you to extend Laravel's validation capabilities to meet your specific requirements, making your application more robust and user-friendly.

Happay Coding!

You can contact me at [wazirially1994@gmail.com] or connect with me at [https://github.com/WAZIRI123] and WhatsApp via:[+255653039317].

Let's turn your Laravel project into a success story together!

Waziri Livewire Toast: A Package to Display Toast Notifications in Laravel

waziri ally amiri — Wed, 01 Nov 2023 11:40:55 +0000

Waziri Livewire Toast is a Laravel package that makes it easy to display toast notifications in your Livewire applications. It is based on the TALL Stack, which means that it uses Tailwind CSS, Alpine.js, and Livewire.

Requirements

To use Livewire Toast, you will need to have the following installed:

Livewire
TailwindCSS
Alpine.js

Installation

To install Livewire Toast, run the following command:

composer require waziri123/waziri-livewire-toast:dev-master

Once Livewire Toast is installed, you need to publish the configuration files and views:

php artisan vendor:publish --tag=config
php artisan vendor:publish --tag=views

Usage

To use Livewire Toast, simply add the following component to your app layout:

@livewire('livewire-toast')

Once you have added the component to your app layout, you can start displaying toast notifications by calling the following methods from your Livewire components, controllers, or views:

Livewire::emitTo('livewire-toast', 'show', 'Project Added Successfully'); // Will show a success message
Livewire::emitTo('livewire-toast', 'showError', 'There was an Error!'); // Will show an error message

// You can also specify the type and message of the toast notification as an array:
Livewire::emitTo('livewire-toast', 'show', ['type' => 'warning', 'message' => 'This is a warning!']);

Configurations

Livewire Toast comes with a number of configuration options that you can customize to meet your needs. To view the configuration options, open the config/livewire-toast.php file.

Troubleshooting

If you are having trouble getting Livewire Toast to work, please check the following:

Make sure that Livewire, Tailwind CSS, and Alpine.js are installed and configured correctly.
Make sure that you have published the Livewire Toast configuration files and views.
If you are using Tailwind CSS, make sure that you have purged your CSS.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Credits

Waziri123
AscSoftwares

License

Livewire Toast is licensed under the MIT license.

Tall CRUD Generator for Livewire v3

waziri ally amiri — Mon, 23 Oct 2023 12:51:22 +0000

Introduction

The Tall CRUD Generator is a Laravel package that generates Livewire components that support CRUD features without you having to write any code. It is a powerful tool that can help you to quickly and easily create CRUD interfaces for your Laravel applications.

Requirements

The Tall CRUD Generator requires the following:

Laravel
Livewire
TailwindCSS
AlpineJS

Installation

To install the Tall CRUD Generator, run the following command:

composer require waziri123/waziri-tall-crud-generator:dev-master

Usage

Once you have installed the Tall CRUD Generator, you can display the configuration page by including the Livewire component in any view:

HTML

@livewire('tall-crud-generator')

Use code with caution. Learn more
This will allow you to select the model and fields that you want to generate the CRUD interface for. You can also configure a number of other options, such as whether or not to include pagination, sorting, and searching.

Once you have configured the CRUD interface, you can generate the code by clicking on the "Generate" button. The Tall CRUD Generator will generate a Livewire component and corresponding views for the CRUD interface. You can then add the Livewire component to your application's layout and start using the CRUD interface immediately.

Features

The Tall CRUD Generator supports a wide range of features, including:

Pagination
Sorting
Searching
Add form in modal
Edit form in modal
Delete with modal confirmation
Validations
Configurable column order in listing
Configurable field type for form
Configurable order for form fields
Flash messages
Configurable number of records per page
Dropdown to change number of records per page
Relations: BelongsTo and BelongsToMany in listing and form
Display related fields in the listing using eager loading
Display count of related fields in the listing using eager loading count
Ability for user to show/hide columns on listing
Allow user to define filters
Bulk action
Date filters

Troubleshooting

If you are having trouble with the Tall CRUD Generator, please check the following:

Make sure that you have installed all of the required dependencies (Laravel, Livewire, TailwindCSS, and AlpineJS).
Make sure that you have published the package's views:
"

php artisan vendor:publish --provider="WAZIRITALLCRUDGENERATOR\TallCrudGeneratorServiceProvider" --tag=views

If you are using TailwindCSS, make sure that you have compiled the TailwindCSS assets:
"

npm run dev

If you are still having trouble, please open an issue on the package's GitHub repository.

Conclusion

The Tall CRUD Generator is a powerful tool that can help you to quickly and easily create CRUD interfaces for your Laravel applications. It is easy to use and supports a wide range of features. If you are looking for a way to speed up the development of your Laravel applications, I highly recommend checking out the Tall CRUD Generator.

Supercharging Node.js Dependencies with Bun in Your Laravel Project

waziri ally amiri — Tue, 12 Sep 2023 06:02:02 +0000

Introduction:
Recently, I came across an exciting JavaScript tool that got me pumped up – Bun. It's a powerful "all-in-one toolkit for JavaScript and TypeScript apps" that can be considered a worthy alternative to NPM and Yarn, but with one notable difference – it's incredibly fast.

In this blog post, we'll explore how you can leverage Bun as a replacement for NPM and Yarn in your local development environment and discover how it can supercharge your typical Laravel application.

Installing Bun

Getting Bun up and running is a breeze. Depending on your system, you can choose from the following installation methods:

For Mac, Linux, or WSL Users:

curl -fsSL https://bun.sh/install | bash

Homebrew Users:
If you prefer to use Homebrew:

brew tap oven-sh/bun
brew install bun

Please note that Windows users can access an experimental native build of Bun, which comes with limited features for now, but it's a promising start. Features like adding, removing, and installing packages are not fully functional on Windows yet.

Once Bun is successfully installed, you can confirm it by running the following command in your Terminal:

bun --version

Utilizing Bun

Now that Bun is at your disposal, let's see how you can replace NPM and Yarn in your workflow. To demonstrate, we'll work with a fresh Laravel Jetstream application featuring Inertia and Vue.

To install all dependencies from an existing package.json file, simply execute the following command:

bun install

Installing Dependencies with Bun

Adding dependencies with Bun is just as straightforward as you're used to with Yarn or NPM. To install a new dependency, use:

bun add [PACKAGE_NAME]

If you want it as a dev-dependency instead:

bun add -d [PACKAGE_NAME]

And just like the install command, adding new dependencies is remarkably fast.

Removing Dependencies

Need to clean house and remove some dependencies? Bun has you covered there too. Use the rm or remove command:

bun rm [PACKAGE_NAME]

And there you have it! With Bun in your toolkit, you can replace NPM and Yarn, experiencing up to 33x faster performance. Happy coding!

How to Make Your Laravel Local Host Project Globally Accessible Using Ngrok for Client Showcases

waziri ally amiri — Wed, 09 Aug 2023 13:58:22 +0000

Introduction:
In the world of web development, showcasing your work to clients is an essential part of the process. While developing a Laravel project locally provides a controlled environment, sharing your progress with clients or team members who are not physically present can be challenging. Enter Ngrok – a powerful tool that enables you to expose your local server to the internet securely. In this blog post, we'll guide you through the steps to make your Laravel localhost project globally accessible using Ngrok, ensuring smooth client showcases and collaboration.

What is Ngrok?

Ngrok is a tunneling service that creates secure tunnels to your localhost, allowing you to expose your local server to the internet. It provides a temporary public URL that anyone can access, which is incredibly useful for sharing your work during development stages.

Step 1: Installation and Setup

Download and install Ngrok from the official website (https://ngrok.com/download).
Extract the downloaded file and place it in a directory of your choice.
Open a terminal window and navigate to the directory where Ngrok is located.
Authenticate your Ngrok account by running the command: ./ngrok authtoken YOUR_AUTH_TOKEN.

Step 2: Starting Your Laravel Project

Navigate to your Laravel project directory in the terminal.
Start your local Laravel development server by running: php artisan serve.

Step 3: Creating a Public Tunnel with Ngrok

In the terminal, navigate to the directory where Ngrok is located.
Create a public tunnel for your Laravel project by running: ./ngrok http 8000 (assuming your Laravel server is running on port 8000).
Ngrok will generate a temporary public URL (e.g., http://randomstring.ngrok.io) that maps to your localhost.

Step 4: Sharing the Public URL

Copy the Ngrok-generated public URL from the terminal.
Share this URL with your clients or team members, allowing them to access your Laravel project from anywhere in the world.

Tips for a Smooth Client Showcase:

Security Considerations: While Ngrok provides a convenient way to share your local project, be cautious with sensitive data. Make sure to remove or secure any confidential information before sharing the URL.
Debugging and Monitoring: Ngrok offers a web interface (http://localhost:4040) where you can monitor traffic, inspect requests, and view error logs. This can be immensely helpful for debugging during showcases.
Ngrok Custom Subdomains: Ngrok provides an option to create custom subdomains for your tunnels. This can make your URLs more user-friendly and professional. Refer to the Ngrok documentation for more details.
Usage Limits: Keep in mind that Ngrok's free version has usage limitations. For extensive or long-term usage, consider upgrading to a paid plan.

Conclusion:
Ngrok is a fantastic tool that empowers developers to make their local Laravel projects globally accessible, facilitating seamless client showcases and collaboration. By following the steps outlined in this guide, you can confidently share your progress with clients, receive feedback, and ensure that your projects meet their expectations, no matter where they are located. Remember to prioritize security and keep best practices in mind while utilizing Ngrok for your development workflow.

Getting Started with Laragon for Laravel Development

waziri ally amiri — Tue, 08 Aug 2023 06:45:14 +0000

Hey there, fellow developers! 🚀 Are you ready to dive into Laravel development using Laragon? Whether you're a seasoned Laravel developer or just starting out, Laragon can streamline your development process and make your life a whole lot easier. In this post, we'll walk you through the steps to get started with Laragon for Laravel development.

What is Laragon?

Laragon is a powerful development environment and a great alternative to popular solutions like XAMPP or WAMP. It's lightweight, fast, and designed to simplify the process of setting up a local development environment for PHP applications, particularly Laravel projects.

Prerequisites

Before we get started, make sure you have the following components installed on your system:

Windows Operating System: Laragon is specifically designed for Windows.
PHP: Laragon comes with various PHP versions that you can easily switch between.
Composer: The PHP dependency manager, required for Laravel.
Git: Version control is essential for managing your Laravel projects.
Laragon: Download and install the latest version of Laragon from laragon.org.

Installing Laragon

Download and Install Laragon: Head over to the Laragon website and download the latest version of Laragon. Run the installer and follow the on-screen instructions.
Choose PHP Version: After installation, open Laragon and click on the PHP version in the top right corner. Select the desired PHP version for your Laravel project.
Create a New Project: Click on the "Quick create" button in the Laragon interface. Enter your project name, and Laragon will set up a new folder for your project in the www directory.

Why Choose Laragon Over XAMPP and WampServer for Laravel Development?

When it comes to setting up a local development environment for Laravel projects, you have several options available, including Laragon, XAMPP, and WampServer. While each of these solutions has its strengths, Laragon offers some compelling advantages that make it a standout choice for Laravel development. Let's explore why you should consider using Laragon over XAMPP and WampServer:
Lightweight and Fast
Laragon is known for its lightweight nature and impressive speed. Unlike XAMPP and WampServer, which bundle various components that you might not always need, Laragon focuses specifically on the tools necessary for Laravel development. This results in a faster and more streamlined environment that doesn't weigh down your system with unnecessary features.
Laravel-Focused Configuration
Laragon is purpose-built for Laravel developers. It comes pre-configured with settings optimized for Laravel projects, including the latest PHP versions, Composer, and Git integration. This tailored setup saves you time and effort, allowing you to jump straight into coding without the need for extensive configuration.
User-Friendly Interface
Laragon boasts a user-friendly and intuitive interface that simplifies the process of managing your development environment. With Laragon, you can easily switch between PHP versions, manage databases, enable SSL support, and perform other tasks through a clean and organized interface. This is particularly beneficial for developers who prefer a hassle-free experience.
SSL Support Out of the Box
Developing secure applications is essential, and Laragon makes it easy by providing SSL support out of the box. Unlike XAMPP and WampServer, which might require additional configuration for SSL, Laragon simplifies the process, allowing you to work on HTTPS-enabled projects without the headache.
Database Management Made Simple
Laragon simplifies database management by offering a user-friendly interface for creating, importing, and managing databases. This intuitive approach contrasts with XAMPP and WampServer, where database management might involve a steeper learning curve and more complex procedures.
Effortless Multiple PHP Versions
Laragon allows you to effortlessly switch between different PHP versions for your projects. This feature is incredibly valuable for testing and ensuring compatibility with various Laravel versions and extensions. While XAMPP and WampServer also support multiple PHP versions, Laragon's seamless integration sets it apart.
Active Community and Regular Updates
Laragon benefits from an active and passionate community of developers who contribute to its growth and improvement. Regular updates ensure that you have access to the latest features, bug fixes, and security enhancements, making Laragon a reliable choice for your ongoing Laravel projects.

Setting Up a Laravel Project
Open Terminal: Launch the Laragon terminal by clicking on the "Terminal" button in the Laragon interface.
Install Laravel: Use Composer to create a new Laravel project. In the terminal, navigate to your project folder using the cd command and run:

   composer create-project --prefer-dist laravel/laravel .

Configuration: Laragon comes with a .env file already set up. Configure your database settings and any other necessary environment variables in this file.

Running Your Laravel Project

Start Server: In the Laragon interface, click on the "Start All" button to start the Apache and MySQL servers.
Access Your Project: Open your web browser and navigate to http://project-name.test, where project-name is the name you specified when creating the project in Laragon.

Bonus Tips

Database Management: Laragon provides a user-friendly interface for managing your databases. You can access it by clicking on the "Database" button in the Laragon interface.
SSL Support: Laragon supports SSL out of the box, allowing you to develop and test secure applications locally.
Multiple PHP Versions: Laragon makes it easy to switch between different PHP versions for your projects.

Conclusion

Congratulations! You're now equipped with the knowledge to set up a local Laravel development environment using Laragon. This powerful tool will undoubtedly boost your productivity and help you focus on what matters most: building amazing Laravel applications.

If you have any questions, encounter issues, or want to share your own Laragon tips, feel free to join the conversation in the comments below. Happy coding! 🎉👨‍💻👩‍💻

Is there anything you'd like to add or modify in this web post? Let me know, and I'll be happy to help!

DEV Community: waziri ally amiri

How to Use Laravel Blade Templating Engine with a Pure Vanilla PHP Project?

Why you should never use the date validation rule without the data_format rule in Laravel

How to use multiple checkboxes in Livewire3

Empowering Your Laravel Application with Custom Validation Rules

Waziri Livewire Toast: A Package to Display Toast Notifications in Laravel

Requirements

Installation

Usage

Configurations

Troubleshooting

Contributing

Credits

License

Tall CRUD Generator for Livewire v3

Introduction

Requirements

Installation

Usage

Features

Troubleshooting

Conclusion

Supercharging Node.js Dependencies with Bun in Your Laravel Project

How to Make Your Laravel Local Host Project Globally Accessible Using Ngrok for Client Showcases

What is Ngrok?

Step 1: Installation and Setup

Step 2: Starting Your Laravel Project

Step 3: Creating a Public Tunnel with Ngrok

Step 4: Sharing the Public URL

Tips for a Smooth Client Showcase:

Getting Started with Laragon for Laravel Development

What is Laragon?

Prerequisites

Installing Laragon

Why Choose Laragon Over XAMPP and WampServer for Laravel Development?

Setting Up a Laravel Project

Running Your Laravel Project

Bonus Tips

Conclusion