Tangible Bytes

This is a silly one.

I wanted to run Laravel in dev mode but using the compiled js and scss from npm run build via vitejs.

This usually works

but for some reason Laravel was trying to serve js/css from http://localhost:5173/@vite/client

a service I usually run - but I wanted to test the build stuff.

The solution is really simple but not well documented.

Laravel Validation supports rules forcing unique values - but exceptions are usually needed.

For example if you have articles on a site where each has a slug that has to be unique - when you update the article it has to possible to save the article using the slug it already has.

https://laravel.com/docs/10.x/validation#rule-unique

The Laravel Docs have a section Constraining Eager Loads

Which hides a lot of power available to you while loading relationships.

It can be used for more than just “constraints”

If you want to sort your relations by a specific fields, add a count of a nested relationship, or in other ways add to teh query - this is where you can do it.

I am working on a project that makes use React within Laravel.

I didn’t find much support for setting up React tests.

So here are som notes on how I got it working.

I needed to send password reset emails from Laravel with additional data so that depending on how the password reset is triggered the email content varies.

You may not need this, if you can manage multiple types of user via roles and permissions it will be much the simpler route to follow.

In my case I wanted user with different: properties, relationships, routes, password rules, timeouts, and more.

It was worth the pain of setting up two authenticatable models.

InertiaJs does a great job of helping me build React apps on Laravel. The form help does a great job - especially with displaying validation messages.

But I couldn’t figure out how to change data and save the form in one action.

The Laravel database validation rules are more powerful and flexible than I realised at first.

Looking at the Available Validation Rules we can see that Exists and Unique both have the suffix (Database)

This is because the both implement the DatabaseRule trait which offers more power than might be expected.

My Laravel site was working just fine yesterday but after a code-only update today I was seeing 502 errors on some pages

upstream sent too big header while reading response header from upstream, client:

• phpfpm + nginx in kubernetes
• Laravel Https Behind a Proxy

While the solution was hard to find it was easy to implement.