Data & D1

Schema, without a database

tools/schema-compile.php boots your app, runs the migrations against an in-memory SQLite, and dumps the resulting DDL through pragma. Your database/ directory is not touched, no MySQL or Postgres server is involved, and the output isdist/schema.sql + dist/schema.json — the same DDL for a MySQL, Postgres or SQLite source app.

On a fresh checkout with no database file, the build seeds a throwaway SQLite under.cache/ so Laravel can boot for prerendering. It is empty on purpose: it is not your database and not the cloud D1.

The query builder

Parameter binding is D1-safe: booleans become 1/0, dates ISO strings,undefined becomes NULL. The builder is exercised against a real in-memory SQLite integration suite, not only against mocks.

// compiled from PHP, at build time; executed against D1 at request time
const posts = await Post.where('published', 1)
  .orderBy('created_at', 'desc')
  .limit(20)
  .get(db);

Eloquent

A schema-driven subset of the ORM compiles: find/findOrFail,all, where*, orderBy*, limit withfirst/get/count/pluck/value; relations hasMany/hasOne/belongsTo (eager and lazy, and as properties); writes create/updateOrCreate/firstOrCreate/fill/save/delete; fillable, accessors and mutators; casts json, decimal:N, hashed;refresh/increment; soft deletes.

Anything outside that — a custom query scope that calls a PHP function the edge cannot run, for example — fails loud with the failing construct named.

Cache, storage, uploads

Two numbers to keep in mind

D1 Free allows 100k writes a day and 5M reads. The toolchain is shaped around that: cookie sessions write zero rows, the throttle is applied to the routes that need it rather than blanket, and eager loading exists to keep query counts down. Theaudit records which constructs were measured and which were only documented.