https://www.prisma.io/ logo
Join Slack
Powered by
Hi guys, so i’m just trying to play around with He...
# orm-help
w
Hi guys, so i’m just trying to play around with Heroku deployment by seeing if i can deploy one of the example applications specifically node-graphql-auth.
I’m noticing that when i boot up local dev, I have all of the wonderful mutations that are in the directory, but when I deploy to heroku via prisma cloud, I don’t see any of my mutations such as signUp
Any idea whats going on here?
n
The Heroku integration from Prisma Cloud sets up a Prisma server on Heroku. If you deploy a Prisma service to that server, it will expose the automatically generated Prisma API. In the above scenario, nothing touches a Node server, which exposes the application schema fully controlled by you.
w
@nilan! awesome man, you’re always on top of answering questions
🙌 1
so how would I be able to expose the same application schema
or would i have to deploy my own
n
You have to deploy a Node server on your own.
Yup
w
I see — so I guess what would be the ideal scenario of using the heroku integration?
n
When you are looking to deploy Prisma to your own server without hassling with the actual Docker setup, you can use the Heroku integration.
w
This is in regards to the heroku installation flow from prisma cloud?
n
Correct
w
but like you said, with that setup, I am unable to expose custom mutations?
n
Correct
You have to deploy a Node server on your own.
w
great, gonna give this a go
👍 1
trying to convince my friend to not go full lambda on me
n
🙂
well you can actually deploy the GraphQL server to a lambda too
w
and wait 5 years to update an response body
🔜 2
awesome, I think with what’s going for is old school REST
j
@nilan I was trying the same as @wontwon, deploying the graphql-auth example to Prisma Cloud resulting in the same difference in exposed API. I still don’t quite understand why these examples can’t run on Prisma Cloud. Could you elaborate?
Open in Slack
PreviousNext
Powered by