Run prisma migrate deploy in Github Actions pipeline
Prisma PostgresI’m running Postgres + a Next.js/Prisma app in Dokploy on my homelab.
If migrations are to be run as part of CI/CD pipeline, in my case via GitHub Actions, I assume the runner needs direct DB connectivity.
In a homelab setup like mine, does this mean I must expose Postgres publicly? I could update pg_hba.conf to restrict access only for local + Github Action runners IP ranges, but still feels weird to me.
This doesn't feel right to me.
Reference: https://github.com/prisma/prisma/discussions/24571
If migrations are to be run as part of CI/CD pipeline, in my case via GitHub Actions, I assume the runner needs direct DB connectivity.
In a homelab setup like mine, does this mean I must expose Postgres publicly? I could update pg_hba.conf to restrict access only for local + Github Action runners IP ranges, but still feels weird to me.
This doesn't feel right to me.
Reference: https://github.com/prisma/prisma/discussions/24571
GitHub
Question Hello everyone, I'm here to clarify my understanding and actual practise everyone does in the Prod environment. First of all, I have read this documentation here before asking. Im full...
