You can discuss the latest 1.7 release here 🙂 https://prisma.slack.com/archives/C0MQJ62NL/p1524593175000578

I've tried so, so hard to avoid dealing with Docker. 😢 I guess that time is over. Can anyone recommend a basic tutorial?

prisma init

docker-compose up -d

is basically the same as former

prisma local start

🙂

Is the end goal to make Prisma even more flexible and less abstracted to appeal more developer?

I just tried upgrading via yarn and 1.7 is only listing beta versions - any advice?

are any of these changes breaking?

@nhuesmann can confirm, looking into it right now. Thanks! 🙂

Yep!

@weakky with this release we tried to simplify the biggest hurdles and confusions that were brought up from the community. Two big factors were problems with the Docker setup and confusion around server/service/stage.

awesome. Thanks Nilan 🙂

@nhuesmann

1.7.0

is published now:

npm install prisma

@nilan 🙌 and confirmed!

on the server/service/stage and architecture, I am still confused to run prisma is it 2 servers..

those are all great questions, thanks @Ben! 🙂 Indeed, the Prisma server and the GraphQL Server are two distinct entities. I recommend a read of the introduction chapter of our documentation: https://www.prisma.io/docs/reference/introduction/what-is-prisma-apohpae9ju

ok thanks I will check it out. Without reading fully perhaps you could answer a few other basic questions before I can spend a lot of time with this....

Sure 🙂 Please start a new conversation in #general, or here: https://www.graph.cool/forum/c/questions

do all security filters and paging get limited at db level so prisma server isn't brining in more than it needs or some of that happeing in memory

I cannot recall but I think

prisma init

before

1.7

let us initialize with boilerplates and examples. Is this not the case anymore?

That's correct! You can use graphql create to instantiate a boilerplate project