From 9949e2275ec973604a52f0c0d95f445f045bd3f0 Mon Sep 17 00:00:00 2001
From: Stefan Lazic <s.lazic@edynamix.com>
Date: Fri, 7 Aug 2026 17:39:31 +0100
Subject: [PATCH] Database 2

fix for vercel build
---
 Dockerfile   | 8 ++++----
 package.json | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/Dockerfile b/Dockerfile
index e01f2fa..14a3261 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -26,10 +26,10 @@ FROM node:22-alpine AS builder
 WORKDIR /app
 COPY --from=deps /app/node_modules ./node_modules
 COPY . .
-# These database env vars aren't needed to generate the client (no DB
-# connection at generate time) — only real values needed at runtime, never
-# baked in here.
-RUN npx prisma generate
+# `npm run build` runs `prisma generate` itself (see package.json — needed
+# so a plain Vercel/`npm run build` deploy generates the client too, not
+# just this Docker path, which used to have its own separate `prisma
+# generate` step here).
 # `next build`'s page-data collection step imports every route module
 # (including /api/health) to inspect it — that pulls in
 # src/lib/db/prisma.ts, which requires DATABASE_HOST/NAME/USER/PASSWORD
diff --git a/package.json b/package.json
index 73519bb..7322b79 100644
--- a/package.json
+++ b/package.json
@@ -5,7 +5,7 @@
   "description": "Mobile-first barber booking platform — customer, barber and owner experiences in one Next.js app.",
   "scripts": {
     "dev": "next dev",
-    "build": "next build",
+    "build": "prisma generate && next build",
     "start": "next start",
     "lint": "eslint .",
     "typecheck": "tsc --noEmit",