Level 74
Unless you are doing something other than moving the pdf I don't see any real reason to use a queue for it.
May 14, 2020
3
Level 2
Best way to repeatedly dev/test jobs?
I have a job that a user must fill out a form and upload a file with. Based on the form settings the file can be processed in different ways.
Currently I am doing
- fill out form and upload pdf
- php artisan queue:work --once (the job has a throw at the end to send it to failed jobs)
- php artisan queue:failed
- php artisan queue:retry #ID (or just knowing to increment the ID and skip 3 for subsequent retries)
- go back to 2 until I've done iterating on the job
Is there a better way to go about doing this?
Level 2
I said I am processing it in different ways, so yes it is more than moving the pdf
Would it be better to make a new console command and then just have the job call the command?
Level 2
Well nm, I should have just exited instead of throw
- fill out form and upload pdf
- php artisan queue:work --once (exit before the end)
- run above as many times as needed
Please or to participate in this conversation.