From 4905022dd5ffbf882936a30ec018f1cbb2819e9d Mon Sep 17 00:00:00 2001 From: Z8MB1E Date: Sun, 16 Aug 2026 19:39:19 -0400 Subject: [PATCH] feat(config): wire prodMigrations for auto-migrate on prod boot MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Import the migrations array from src/migrations/index.ts and pass it as prodMigrations to the postgres adapter. Per @payloadcms/db-postgres connect.js, when NODE_ENV=production the adapter now auto-runs payload migrate against this array on every boot, so pending migrations apply on deploy without a manual docker exec step. Idempotent on next prod boot since payload_migrations already tracks batches 1-2. DEPLOYMENT.md ยง7's manual 'docker exec ... payload/bin.js migrate' still works as a fallback via filesystem discovery. --- src/payload.config.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/payload.config.ts b/src/payload.config.ts index d16a637..e33471b 100644 --- a/src/payload.config.ts +++ b/src/payload.config.ts @@ -43,6 +43,7 @@ import { MarketListings } from "@/collections/market/MarketListings"; import { MarketNegotiations } from "@/collections/market/MarketNegotiations"; import { UserNotifications } from "@/collections/users/UserNotifications"; import { Tickets } from "@/collections/tickets/Tickets"; +import { migrations } from "./migrations"; import { nodemailerAdapter } from "@payloadcms/email-nodemailer"; import nodemailer from "nodemailer"; @@ -146,6 +147,7 @@ export default buildConfig({ connectionString: process.env.DATABASE_URI || "", }, push: process.env.NODE_ENV === "development", + prodMigrations: migrations, }), sharp, bin: [