development workflow with multiple devs and ci/cd

[koraysels]

note: have found similar discussions, but never a complete example/explanation as to how to handle dev to stage/prod trasnition wiht postgres

We are trying to streamline or development workflow but we are having lots of issues work postgres and ci/cd.

What is the correct way of building an application with Payload cms 3 and nextjs ?

Right now, we have

• local dev against local Postgres and S3 (for uploads)
• PR development flow (using github pull requests)
• automatic branch deployments using Netlify and an online Postgres DB <-- This is where we get stuck..

If I accept a merge request and pull it into my system, I get all sorts of errors and questions when running pnpm dev. I always have to run payload migrate:fresh to get it to work again locally..

How can I get it to work online with the hosted DB? I tried to create migrations and run them in a build step, but I get warnings and interactive questions like :

4:14:27 PM: $ NODE_OPTIONS=--no-deprecation pnpm build:netlify
4:14:27 PM: > @1.0.0 build:netlify /opt/build/repo
4:14:27 PM: > cross-env NODE_OPTIONS=--no-deprecation pnpm migrate && pnpm build
4:14:27 PM: > @1.0.0 migrate /opt/build/repo
4:14:27 PM: > cross-env NODE_OPTIONS=--no-deprecation payload migrate
4:14:30 PM: [14:14:30] WARN: No email adapter provided. Email will be written to console. More info at https://payloadcms.com/docs/email/overview.
4:14:30 PM: [14:14:30] INFO: Reading migration files from /opt/build/repo/src/migrations
4:14:30 PM: ? It looks like you've run Payload in dev mode, meaning you've dynamically pushed changes to your database.

And then it just hangs.. what is the correct flow here? we are obviously mixing push and migrations, but I can't wrap my head around it...