https://www.prisma.io/ logo
Join Slack
Powered by
I am also a little worried how quite this communit...
# orm-help
d
I am also a little worried how quite this community is for a slack channel with 41,000 members….
j
I wouldn't be. It's an evening in the US, and it's certainly not the only large community I've been in where there's only a small subset that contribute. At any rate during Prisma's business day they usually have folks around who are regularly responding
💚 2
👌 1
d
Im basing this off the history, seems a lot of people just dumping questions with no answers. Is there a more official support community in the form of a forum?
j
seems a lot of people just dumping questions with no answers
That is not my experience at all. When I've asked questions I usually get a response within a day
Keep in mind we're also just coming off the holidays
👍 1
d
👍
Just seems odd there is no existence of testing on the entire prisma site…..
Im guessing there isnt a lot of real apps with prisma in prod yet… 😕
j
There isn't any mention on testing on other ORM websites either: https://sequelize.org/master/ https://typeorm.io/
And they've been around for ages
From my understanding people tend to mock their datastores and never touch a DB at all in tests
(Which seems liable to miss things from my perspective, but it is significantly faster and requires less overhead)
As far as deployment: Seems to me like that's largely on whatever framework you may be using rather than Prisma. Prisma's just a library, you're not using it in a vacuum
(And for migrations... I mean, you need to run your migrations when you deploy your app)
RE:
I also find it strange that Prisma can be prod ready, but migrate is only beta? Who is actually using prisma without migrate?
The initial use case was introspection of existing DBs. The intent is that the Prisma query library and Prisma migrate are two completely separate components and you can use one, the other, or both - in the early days of Prisma v2 they even had entirely different names
d
When ever there is a deploy process (migration / generate) there should be test and CI/CD documentation.
j
What type of information would you be expecting about CI/CD?
To be honest I'm not clear what that would actually mean for a library like this
Just guidance for how to execute migrations?
And what would that mean beyond the documentation elsewhere about how to run migrations?
d
We run tests by actually executing http requests to our graphql server for example, so prisma needs to be easily configurable for a testing environment.
As for CI/CD i just always feel let down when I see “Deploy to Heroku” and its no where near how you would actually deploy.
There should be guides to actually setup a real app with actual CICD with tests using CircleCI or Github Actions in my honest opinion.
j
Again, that's not really the responsibility for this library... you'd use Prisma within the context of another framework, like Nest, Nexus, Feathers, etc
As far as what it means to deploy
Prisma will happily tag along with whatever Node project you're running it within
And as or testing... I mean, you can specify a connection string. Not sure what else you'd need to configure. i guess having best practices wouldn't hurt though
n
Thanks so much for chiming in here @Jonathan Romano, I can subscribe to everything you said! 🙌 @Dan I want to add to a few things!
Im basing this off the history, seems a lot of people just dumping questions with no answers. Is there a more official support community in the form of a forum?
We've indeed slowed down our support over the holidays. If you go back to the week before the 23rd of December, you'll notice that pretty much all requests on Slack receive an answer. So far we have been able to manage this Salck community quite well I think 🙂
Just seems odd there is no existence of testing on the entire prisma site…..
As for your request about testing and CI/CD workflows, as we discussed on Twitter, I fully agree that we're lacking proper guides for this right now. This is something we definitely want to work on! I'm looking forward to your GitHub issue in the docs repo with some concrete questions that we can address in the docs 🙂
I also find it strange that Prisma can be prod ready, but migrate is only beta?
Prisma consists of several components that each have separate responsibilities. Prisma Client and Prisma Studio are battle-tested and ready for production. Prisma Migrate has been released in Preview a couple of weeks ago and is certainly in a usable state – but might have some subtle quirks. We want to make sure the software we release for GA is completely stable, that's why it's still behind a preview flag – the more feedback we get for it the sooner we can release it for GA 🙂
🚀 1
j
Just my 2 cents, but from my perspective, the folks at prisma have been super responsive to most questions, and I think the prisma2 channel is where you would see more life than the general chat
👌 1
👍 1
d
Hey Dan, If you’re interested in testing an API, this is covered in the following blog post: https://www.prisma.io/blog/backend-prisma-typescript-orm-with-postgresql-rest-api-validation-dcba1ps7kip3#create-a-test-for-t[…]he-create-user-route. It’s specific to Hapi and REST but the same principles apply. You can also look how that’s integrated with CI/CD in a follow up article: https://www.prisma.io/blog/backend-prisma-typescript-orm-with-postgresql-deployment-bbba1ps7kip5 which uses GitHub actions to spin up a DB run tests and deploy.
❤️ 3
Open in Slack
PreviousNext
Powered by