Initial setup doesn't work with PostgreSQL & migrations in production?

.nobeylast year

6

FROM node:21 as base

RUN mkdir -p /home/node/app && chown -R node:node /home/node/app

WORKDIR /home/node/app

FROM base as build

COPY --chown=node:node package.json package-lock.json /home/node/app/
COPY --chown=node:node tsconfig.json /home/node/app/
COPY --chown=node:node src /home/node/app/src

RUN npm install
RUN npm run build

FROM base as runtime

ENV NODE_ENV=production
ENV PAYLOAD_CONFIG_PATH=dist/payload.config.js

COPY --chown=node:node package.json package-lock.json /home/node/app/
RUN npm ci --omit=dev

COPY --chown=node:node --from=build /home/node/app/dist /home/node/app/dist
COPY --chown=node:node --from=build /home/node/app/build /home/node/app/build

USER node

CMD npx payload migrate && node dist/server.js

• 

  pedogunulast year

  You have to specify migration directory.

  
  https://payloadcms.com/docs/database/migrations#migration-file-contents
  

  Payload stores all created migrations in a folder that you can specify. By default, migrations are stored in ./src/migrations.
  

  There are

  migrationDir

  option in

  mongooseAdapter

  and

  postgresAdapter

  .

• 

  .nobeylast year

  Cool, so that answers my second question. I don't actually have any migrations yet, it was just for future reference. That doc also mentions that

  
  

  Payload will check the default and possibly make a best effort to find your migrations directory by searching in common locations ie. ./src/migrations, ./dist/migrations, ./migrations, etc.
  

  but I guess it makes sense to be explicit for my app! Thanks!

• 

  jmikrut

  last year

  hey @nobey - good to see you here!

  
  

  
  

  how are migrations supposed to be ran in production when I don't include the src directory in my final build?
  

  
  

  that's really up to you and your build process - i.e. if you are only including your

  /dist

  folder, then you can run them from

  /dist
  

  
  

  it doesn't really matter if you run them from

  /src

  or

  /dist
• 

  .nobeylast year

  That part makes sense. Do I need to write migrations for each of the collections & fields I create then to get this up and running in production with Postgres? Locally, I can just create the different schemas and the collections just show up in the Admin panel without me having to do anything, but this isn't the case in production.

• 

  jmikrut

  last year

  I am actually going to do a video on this

  
  

  
  

  but the TL;DR

  
  

  
  

  1. use push mode in dev, get everything to a spot where you're happy with it (feature completed, etc)

  
  

  2. then create a migration

  
  

  3. then ONLY run the migration against your non-dev DBs before you deploy your new code

• 

  .nobeylast year

  Got it, I was assuming Payload would handle and apply schema changes under the hood. This might prompt some more questions down the line once I use it a bit more. There wouldn't happen to be a payload command to generate migrations based on the current schema, would there? 😅 Maybe a roadmap item 😉

  
  
  

  Thanks for the help!!

  
  

  
  

  Never mind, this is already a thing!

  npm run payload migrate:create

  -- cool! Thanks again 🙂

  https://payloadcms.com/docs/database/postgres#migration-workflows