"Real-World Heroku" development - Using Prisma on Heroku Review Apps

[JamesHenry]

Hi there!

Background

@marktani recommended that I turn my slack thread into a GitHub issue so that he and others could give feedback in a more centralised way.

I am working with the new Heroku integration, it’s so easy to get started, great work!

However, now that I am trying to make my setup a bit more real world, some things are not entirely clear.

Problem

The thing I really want to be able to do is make use of Heroku’s Review Apps feature - to deploy a new app for each PR I open to my repo which contains my Prisma server logic and my custom API on top of it.

For me, this is a very standard idea - we need to be able to run a mixture of automated and manual testing when making updates to any code, and our prisma server is no exception.

Because the Prisma-Heroku integration is so "magical", a lot of the configuration is naturally opaque to us as users, but in order to set up my Review App I think I need to recreate the commands/setup that Prisma is running behind the scenes when we make use of the integration.

I can seemingly get a fresh database configured for each Review App (using a combination of heroku.yml and app.json), but I am unclear on how to start a fresh prisma service for the Review App, because how that is controlled is what is somewhat hidden.

It seems to me that the awesome folks at Prisma must be intimately familiar with how to configure Heroku, as they setup such a slick integration, so I think my question boils down to:

What I'm missing...

Is there a Dockerfile/script or equivalent that the Prisma folks can point us to so that we can wire all this together for Heroku review apps?

Thanks!

[LawJolla]

Thanks @JamesHenry for raising this issue! I'm very interested how Prisma and Heroku pipelines can be integrated!

[arush]

+1