Seed

@halostack/seed resets Postgres and seeds a demo account alongside a batch of random todos. You run it through the root bun run db:seed command, and it's also part of the bun run setup bootstrap. It isn't a library — it has no exports, just a CLI entrypoint.

Structure

The seeder is broken into an orchestrator and two focused steps:

• src/index.ts — the orchestrator, which runs migrate → reset → seed in order.
• src/auth.ts — creates the demo user and organization through better-auth's API, so the password is properly hashed rather than inserted as a raw row.
• src/todos.ts — generates random todos with drizzle-seed, then realigns the todos identity sequence afterward so the app's own inserts don't collide.

Running

The default run migrates, resets the data (TRUNCATE … RESTART IDENTITY), and seeds. Flags let you tune the volume, reproducibility, and behavior:

Copybun run db:seed                # migrate, reset (TRUNCATE … RESTART IDENTITY), seed
bun run db:seed --count=100    # number of demo todos (default 25)
bun run db:seed --seed=42      # fix the PRNG seed for reproducible todos
bun run db:seed --skip-reset   # append instead of truncating
bun run db:seed --force        # required when NODE_ENV=production

The result is a demo login of [email protected] / password, owning a "Demo Org".

Conventions

Auth identities always go through @halostack/auth (never raw inserts) so that password hashing and organization wiring match production exactly. CLI logging and reporting use @halostack/scripts, and the database connection and flags are read from @halostack/env.