Tightening CSP for a Laravel + Vite front end
Content-Security-Policy with hashed assets, nonces, and the traps of inline scripts.
- Laravel
- Architecture
Content-Security-Policy with hashed assets, nonces, and the traps of inline scripts.
Correlation IDs, levels, and context fields beat walls of printf debugging.
Boundaries follow team and scaling pain—not conference keynotes.
Keeping design tokens and markup co-located without turning every file into a class soup.
Composite indexes are not free—order columns the way your WHERE and ORDER BY clauses read.
A single Redis instance can back several cross-cutting concerns if you name keys consistently.
URL prefixes, headers, and sunset policies—pick one story and stick to it.
Offloading slow work is not only about speed—it is about predictable failure domains.
Using Pest to lock down authentication, validation, and happy paths without brittle browser tests.
What changed in the default skeleton, and how it affects day-to-day development.