- Author
- Pre-Knowledge about artisan
- artisan all lines of code explained
- What I discovered on artisan analysis
- Most artisan used commands
- Make your own artisan commands
Navigating the Laravel ecosystem has been challenging due to the scarcity of up-to-date resources. Despite some efforts to find current information, I've encountered deficiency of resources that accurately reflect the latest changes in Laravel. This discrepancy has made it particularly challenging to understand the many advancements and updates introduced in versions beyond Laravel 11. Consequently, I've found myself grappling with outdated materials, hindering my ability to grasp the wonders of the latest Laravel iterations.
As per the Laravel documentation, the artisan file serves as the entry point for Laravel's Command Line Interface (CLI), enabling direct execution of Laravel commands from the CLI of your operating system.
Let's examine the artisan file line by line:
#!/usr/bin/env phpThis is the shebang or hashbang line. If you're familiar with bash scripting, you'll recognize its purpose. It specifies the interpreter that should be used to execute the following script, in this case, PHP.
While this line isn't mandatory, including it ensures compatibility across different environments. Additionally, if PHP is installed in a non-standard location, adjusting the shebang line accordingly is essential.
<?php
use Symfony\Component\Console\Input\ArgvInput;
The <?php tag starts the PHP script. The use statement brings in the ArgvInput class from the Symfony\Component\Console\Input group. This class, which is part of the Symfony Console part, is used by Laravel for commands on the command line. At first, I was confused because I didn't see the Symfony folder at the main level. But I looked closer and realized that these parts are managed by the symfony library inside the vendor folder. Also, I noticed something interesting: the use was used before any include or require lines. Later, I found out that this line could be moved after the require statement (after line 9) and it would still work fine.
define('LARAVEL_START', microtime(true));
This line defines the constant LARAVEL_START, which stores the value returned by the microtime function with the parameter true. This function returns the current Unix timestamp with microseconds. Although its primary purpose is to initialize a timer to measure the framework's boot-up time, I haven't encountered instances of its usage within the framework itself. Perhaps its utilization could be explored independently.
Look in this example we can test the
LARAVEL_STARTconstant:As a PHP artisan it is very crutual to love performance and test performance in your application that is how you can test the actual performance!.
The line before this one tells us that it's adding the Composer autoloader. Even though the libraries here are from Composer and not specifically for Laravel, let me explain a bit. This line brings in the Composer autoloader file to our script. Composer creates this file, and it's in charge of finding and loading classes and files from all the libraries we installed with Composer. When we include this file, Laravel can automatically find and use all the classes from the libraries we added with Composer. This helps keep our code organized and makes managing dependencies easier. So, once we include this file, we can use all the classes without any extra effort.
The vendor/autoload.php file, accessible here, handles autoload functionality. I won't delve further into its details as it falls outside the scope of Laravel-specific discussion.
// Bootstrap Laravel and handle the command...
$status = (require_once __DIR__.'/bootstrap/app.php')
->handleCommand(new ArgvInput);
exit($status);
After including app.php(using require), it obtains an instance of our Laravel application.
Then, it uses this application instance to run a command through Artisan, Laravel's command-line tool. The command execution result, such as success or failure, is stored in the $status variable.
Then you can know what is going on bootstrap/app.php, here
If you want to see where are the commands stored and logic implemented on their actions, go here
php artisan list # This command will list available Artisan commands
php artisan help migrate # Replace 'migrate' with any command you want to see its documentation
php artisan # Same as 'php artisan list'
php artisan make:controller Admin/HomeController # This create a controller inside a Admin folder, like this app/Http/Controller/Admin/HomeController
php artisan make:model Logs # This creates a Logs model like this app/Models/Logs
php artisan make:middleware FilterAllowedUsers # This filter the http request coming to the application using custom filtering/logic, Remember to register them
php artisan migrate # Do the migration to your laravel application
php artisan migrate:fresh # Deleting the all the tables and do the migration again
php artisan db:seed # Populate your database with seeders
# Have your favourite command? then pull request :)If you want to run your Laravel application on a specific port, such as port 80, you can execute the following command:
php artisan serve --port=80Additionally, you can specify the server's IP address along with the port:
php artisan serve --host=0.0.0.0 --port=80Also you can customize your own commands using this command:
php artisan make:command MyCustomCommandLook at app/console/Commands to edit your custom command, for more details go here
Feel free to explore my the whole roadmap.