FREE ARCHIVE

Articles

33 write-ups on Laravel in production. Every one has runnable code and a link to the repo.

ALL QUEUES VALIDATION ELOQUENT TESTING AI & LLMS DEPLOYMENT PERFORMANCE FILAMENT

// showing 9 of 33 · sorted by newest

TAGS #horizon #pest #pgvector #octane #livewire #stripe

exclude_unless dropped the field and required never fired

The client omitted one field and the validator silently discarded a different one. validated() came back without it, the required rule never fired, and update() kept the old price.

Oct 9, 2026

VALIDATION / 6 MIN

exists validated a row you already soft deleted

Your form request accepts a project_id that passed the exists rule. The project was deleted three weeks ago. The rule never looked at deleted_at, and the model class you passed it did not help.

Oct 5, 2026

VALIDATION / 7 MIN

The unique rule ignored nothing and the row failed itself

Your update form rejects the email address the record already owns. You passed the model to ignore() as documented, the id it extracted was falsy, and the rule dropped the exclusion.

Oct 5, 2026

VALIDATION / 6 MIN

validated() handed create() the keys you never validated

You used validated() instead of all() because it is the safe one. With an array field and no nested rules, it returns every key the client sent, including the ones you never wrote a rule for.

Oct 5, 2026

PERFORMANCE / 6 MIN

Collection::where() loaded your whole table to filter it

The same method name does two completely different things depending on whether a get() came before it. One filters in the database; the other filters in PHP, loosely.

Oct 1, 2026

PERFORMANCE / 7 MIN

Offset pagination skipped a row and repeated another

A reviewer worked through every page of the queue and still missed a record. The row was never on a page — it fell into the gap that OFFSET opens when the table moves underneath it.

Oct 1, 2026

DEPLOYMENT / 7 MIN

Storage::url() returns a 404 and the file is right there

You can SSH in and cat the file. The browser gets a 404. Three different mechanisms produce that exact symptom, and one of them reports success while failing.

Oct 1, 2026

ELOQUENT / 7 MIN

The transaction retried and the email went out three times

You passed a second argument to DB::transaction() to survive deadlocks, and it worked. The unit it retries is the whole closure, so everything inside it ran again.

Oct 1, 2026

AI & LLMS / 8 MIN

Rate limits, and the retries that make them worse

Http::retry(3) waits zero milliseconds between attempts and retries a bad API key three times. Here is what each retry layer actually does, and what it bills you for.

Sep 23, 2026

Load older articles