Laravel queue is quite easy to setup and use.
But how it actually work is seem like a mystery and undocumented
There are some pitfall that beginner usually fall into, the common one is stucking
Laravel queue is quite easy to setup and use.
But how it actually work is seem like a mystery and undocumented
There are some pitfall that beginner usually fall into, the common one is stucking
Laravel is awesome, but personally I don’t appreciate their documentation as it seems always “beginner orientated”.
They trend make simple things automagically happen, without let you knowing how it works.
They you get into trouble when you need advanced functionality.
Say, you get this boilerplate when typing php artisan make:job TestJob
:
<?php namespace App\Jobs; use Illuminate\Bus\Queueable; use Illuminate\Queue\SerializesModels; use Illuminate\Queue\InteractsWithQueue; use Illuminate\Contracts\Queue\ShouldQueue; use Illuminate\Foundation\Bus\Dispatchable; class TestJob implements ShouldQueue { use Dispatchable, InteractsWithQueue, Queueable, SerializesModels; /** * Create a new job instance. * * @return void */ public function __construct() { // } /** * Execute the job. * * @return void */ public function handle() { // } }
So, what actually are ShouldQueue
, Dispatchable
, InteractsWithQueue
, Queueable
, SerializesModels
?
Documentation won’t tell you, even if you read the API Reference, you have little idea what they means.
You likely encounter those problem when developing Laravel Application using Windows Machine.
.env
is set to different credential.env
setting drifting between two separate Laravel installations (e.g. http://127.0.0.1:8080 .env setting applied to http://127.0.0.1:8081)Continue reading “[Windows] Laravel behaving strange on Windows Server”