From fff8c0da261a002b6fa651c7448e6577ac2060d3 Mon Sep 17 00:00:00 2001
From: Nicolas <nicolaslef53@gmail.com>
Date: Tue, 18 Aug 2026 00:04:14 +0200
Subject: [PATCH] fix(api): seed reference data (diets/allergies) on container
 start
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Found on http://batch.dev.kyuno.fr/: GET /reference/diets and
/reference/allergies both returned [] — onboarding's "régime
alimentaire" step and the profile's food-preferences tab had nothing to
show. Cause: the Docker image's CMD only ran `prisma migrate deploy`
(schema), never the seed that populates Diet/Category/Allergy.

Adds src/scripts/seed-runtime.ts — a runtime-only seed entry point
(distinct from prisma/seed.ts, the dev-time one wired to `prisma db
seed`/`prisma migrate reset` via tsx importing from ../src, which isn't
shipped in the runtime image). This one lives under src/ so tsc compiles
it into dist/ alongside everything else, and runs via plain `node`,
reusing the same idempotent seedReferenceData() (upserts by unique name)
already used by prisma/seed.ts and test-support/reset-db.ts.

Dockerfile CMD now runs it between migrate deploy and starting the
server — safe on every container start/restart, confirmed idempotent
locally (no duplicates, no error on a second run against an
already-seeded database).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 apps/api/Dockerfile                  |  8 +++++---
 apps/api/src/scripts/seed-runtime.ts | 27 +++++++++++++++++++++++++++
 2 files changed, 32 insertions(+), 3 deletions(-)
 create mode 100644 apps/api/src/scripts/seed-runtime.ts

diff --git a/apps/api/Dockerfile b/apps/api/Dockerfile
index 08cffa3..9e4441a 100644
--- a/apps/api/Dockerfile
+++ b/apps/api/Dockerfile
@@ -42,6 +42,8 @@ COPY --from=build /repo/apps/web/dist ./apps/web/dist
 
 WORKDIR /repo/apps/api
 EXPOSE 3000
-# Applies pending migrations before starting — keeps the review environment's
-# schema in sync automatically, no manual step needed.
-CMD ["sh", "-c", "node_modules/.bin/prisma migrate deploy && node dist/server.js"]
+# Applies pending migrations, then seeds the reference data (Diet/Category/
+# Allergy — see src/scripts/seed-runtime.ts) before starting. Both steps are
+# safe to repeat on every container start: migrate deploy only applies
+# pending migrations, and the seed upserts by unique name.
+CMD ["sh", "-c", "node_modules/.bin/prisma migrate deploy && node dist/scripts/seed-runtime.js && node dist/server.js"]
diff --git a/apps/api/src/scripts/seed-runtime.ts b/apps/api/src/scripts/seed-runtime.ts
new file mode 100644
index 0000000..5044d91
--- /dev/null
+++ b/apps/api/src/scripts/seed-runtime.ts
@@ -0,0 +1,27 @@
+import { prisma } from "../db/prisma.js";
+import { seedReferenceData } from "../db/reference-seed-data.js";
+
+/**
+ * Runtime seed entry point for the production Docker image — run via
+ * `node dist/scripts/seed-runtime.js` in apps/api/Dockerfile's CMD, after
+ * `prisma migrate deploy` and before starting the server.
+ *
+ * Deliberately separate from `prisma/seed.ts` (the dev-time entry point
+ * wired to `prisma db seed`/`prisma migrate reset`): that one imports
+ * `seedReferenceData` from `../src/db/...` and runs via `tsx`, but the
+ * runtime image only ships compiled `dist` output, not `src` (see the
+ * Dockerfile) — this lives under `src/` instead, so `tsc` compiles it
+ * alongside everything else, and it runs under plain `node`, no tsx
+ * needed at runtime.
+ *
+ * Safe to run on every container start: `seedReferenceData` upserts by
+ * each row's unique name, so re-running it against a database that
+ * already has this data is a no-op.
+ */
+seedReferenceData(prisma)
+  .then(() => prisma.$disconnect())
+  .catch(async (err) => {
+    console.error(err);
+    await prisma.$disconnect();
+    process.exit(1);
+  });