GUIDES
Compression and resizing are two genuinely separate optimizations that Intervention Image happens to handle in the same fluent chain — applying both together is what typically produces the biggest file-size reduction.
How to scaffold, argument/option-flag, and register a custom php artisan command — including the one config step people forget when it does not show up in the command list.
The one crontab entry that runs everything, why it must fire every minute, and how scheduled tasks are actually defined in Laravel 11 versus older versions.
PHP's ZipArchive extension does the actual work here — Laravel adds essentially no abstraction on top of it, which is genuinely fine, since the native API is already fairly simple for the common cases.
Laravel logs everything to a single laravel.log by default. Here is how to split payment, webhook, or auth events into their own dedicated log files with a custom channel.
The scroll listener itself is the easy part — checking whether more pages actually exist, and preventing duplicate simultaneous requests, are what separates a working implementation from a buggy one.
A dedicated log channel keeps one specific event stream (payments, webhooks) in its own file — genuinely easier to monitor and grep than digging it out of the shared laravel.log alongside everything else.
Gmail SMTP config for Laravel Mail, and why you need an App Password, not your normal Gmail password, once 2-Step Verification is on.
Reducing an uploaded image's file size without resizing it, using Intervention Image — and why compression quality and visual quality are not the same tradeoff for every image.
Creating several resized versions of an uploaded image on the fly with Intervention Image — a small thumbnail, a medium preview, and the original — and why doing this at upload time beats resizing on every request.
File::deleteDirectory() removes a folder and everything inside it in one call — there's no built-in confirmation step, so a wrong path here is a silent, unrecoverable, one-shot operation.
File::put() and File::append() do genuinely different things despite the similar-sounding names — one replaces a file's entire contents, the other adds to whatever's already there.
