I'm confused about the best practices for dev/prod workflow after having deployed Prisma on docker... I guess it's safest to develop aginst a dev instance (eg Prisma cloud) while production api connects to docker (production) instance. If I make changes in schema between versions then, how would I deploy changes without breaking live app? ... I realize this is not neccessarily a Prisma question but asked here since Prisma is what I'm learning from, just wondering if there are any tutorials/guides on this for common patterns migrating Prisma?

Still no clear way to migrate stuff on prisma schemas are easily extended but that's about it (new fields without any other modification) References: https://github.com/prisma/prisma/issues/1263 https://github.com/prisma/prisma/issues/2323

I see... will be following that discussion. Would you recommend still to have 2x Prisma instances, eg. dev on Prisma cloud and production on docker ?

So the following is going to be very opiniated: I use kubernetes and k8 has a nice isolation mechanism called namespace which I use for the rest of my INFRA also. I would assume that the way prisma is build, that they would prefer to have single instance with multiple environaments (aka stages in prisma linguo)