Skip to content

Commit 68ff63e

Browse files
prc5claude
andcommitted
docs: ✏️ quick start creates the initial migration instead of deploying none
The repo ships the schema but no migrations, so the 'prisma migrate deploy' step reported 'No migration found' and left the database empty while looking like it worked. 'migrate dev --name init' creates and applies the initial migration (and regenerates the client on the way). The pnpm filter also matched nothing: the package is @hype-stack/backend and create renames the scope besides, so filter by directory. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent 2dbe712 commit 68ff63e

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

‎README.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -221,9 +221,8 @@ npx @hype-stack/cli create
221221
# Start infrastructure
222222
cd apps/backend && docker compose up -d && cd ../..
223223

224-
# Run migrations
225-
pnpm --filter backend exec prisma migrate deploy
226-
pnpm --filter backend exec prisma generate
224+
# Create and apply the initial migration (the repo ships the schema, not migrations)
225+
pnpm --filter ./apps/backend exec prisma migrate dev --name init
227226

228227
# Launch everything
229228
pnpm dev

0 commit comments

Comments
 (0)