Should I keep query business rules in Eloquent local scopes or in a repository layer?
Keep query rules in local scopes and test them against a real database; add a repository only when the domain genuinely has to decouple from Eloquent.
Tag
Building applications with Laravel: Eloquent, queues, authentication and version upgrades. Questions under this tag, answered directly.
13 answered questions carry this tag.
Keep query rules in local scopes and test them against a real database; add a repository only when the domain genuinely has to decouple from Eloquent.
With 3 stable types and a real need for foreign keys, use a single-table exclusive arc; if the type set is open-ended, go pure morph with a morph map.
Use chunkById() when there is real per-row work and never touch the cursor column; if you only update a column, switch to one set-based UPDATE.
Pin the user with a build-time ARG UID, use COPY --chown, and for named volumes chown only storage and bootstrap/cache in the entrypoint.
Integer cents in the DB, an immutable Money on the model: put the mapping in one CastsAttributes class and keep currency as a second column there.
Run it fully strict and throwing in local and CI; in production keep it on but wire handleLazyLoadingViolationUsing to log without failing the request.
The tunnel is sound but makes Cloudflare your only way in; stay on the current Caddy setup, lock the origin to Cloudflare's IP ranges and add origin pulls.
Add the column nullable, move the backfill to a separate throttled step, run migrations in their own stage, and drop the old column in a later release.
After flipping the symlink, gracefully reload PHP-FPM rather than restarting it; on Octane, octane:reload is mandatory and opcache_reset is optional.
Put tries and a backoff on the job so it lands in failed_jobs at the cap, alert from a JobFailed listener and replay it with queue:retry.