DuskDuskv1.0.0
[]previous and next page

Checklist

Checklist in the Databases guide.

For agentsUpdated
  • The connection string and tokens are read in .server modules, from process.env, and are listed in the deployment's secrets, not in DUSK_PUBLIC_* variables (those are shipped to the browser).
  • One client per process, kept on globalThis so dusk dev does not leak connections.
  • Migrations run at deploy time, before the new version takes traffic.
  • Every database error that the caller can fix is mapped to an HttpError with the right status; the others reach onError.
  • Writes that belong together share a transaction.
  • On an edge runtime the client is an HTTP one, and nothing opens a file or loads a native module.