Tangible Bytes

A Web Developer’s Blog

Laravel Database Privileges

Laravel has some really good features for setting database connections - but oddly this isn’t spelled out in the documentation.

Databases (especially in Docker containers) often come by default with a single, powerful, user account.

As a result all too often people run Laravel without considering the principle of least privilege.

By following a few simple steps we can enhance security.

Read more ...

Laravel Migrate - Exclude Tables

Laravel’s database migrations is a great system and makes it easy for the development team to stay in sync with schema changes as well as ensuring tests can run against a defined database state.

It also makes great use of transactions to efficiently roll back changes after each test

But what if you have some large tables of fairly static data that you don’t want to reload on every test run …

Read more ...

Laravel Database Model

Something didn’t quite click with me about Laravel Eloquent Models.

There is nothing in the Model that defines the fields.

The Model defines which database table the data is stored in.

Whatever fields are in the table will be loaded to the Model.

Read more ...

Laravel Database Testing

I wanted to better understand what is happening when I run Laravel tests that hit the database.

TLDR: Database migrations are run on every test run, optionally with seed data.

Each test case runs in a transaction.

(This is written based on Laravel 9)

Read more ...

Laravel Versions

How to find out what version of Laravel you have.

The difference between a laravel-framework update and a laravel skeleton update.

What is Laravel skeleton anyway ?

How to control when you get updates.

Read more ...

Laravel Route Binding Null/Empty Object

Laravel’s routing and binding is nice

But when I got it wrong I didn’t get the kind of error I expected

Laravel automatically resolves Eloquent models defined in routes or controller actions whose type-hinted variable names match a route segment name.

use App\Models\User;
Route::get('/users/{user}', function (User $user) {
    return $user->email;
Read more ...