Seeing this on the

node-basic

template from prisma init:

src/index.js:48
    ...req,
    ^^^

SyntaxError: Unexpected token ...

@nilan only to be sure 🙂 is prisma the right thing for me now or the graphcool 1.0 rc1 i want to use all of your services just want to have my own graphql schema for the application

what's the relationship between local docker and prisma CLI supposed to be? I noticed that it just sorta spawns some containers but doesn't have a compose file or anything like that.

Speaking of Docker, are the images listed on docker hub like "prismagraphql/prisma" from you guys?

It's not really transparent, can't see the docker file etc

Is Graphcool Cloud already using the latest Graphcool Framework based on Prisma 1.0?

is there a way to eject the local cluster as you could with graphcool?

Can anyone help a dummy like me see the moving parts here? Prisma = a graphql layer above my (for now mysql-only, but expanding in future) db. And Prisma will also (eventually?) be the layer above the GraphCool hosted database/platform service? Or is GraphCool Inc getting out of the hosted platform/database business and getting into some kind of Prisma-layer-above-any-database-you-want business w/ some kind of Prisma cloud dashboard services?

One thing I would like to see out of the Graphcool staff is an explicit definition of what Graphcool Framework contains. I know a major component is Prisma, but what else? Serverless functions is one thing that's listed, but even then, what does that mean? If Graphcool Framework is open source, what OSS component implements serverless functions? That kind of idea.

i gotta say i've never been so confused with all the churn and name changes, etc... @schickling I think a diagram or something visual that shows how each prizma/graphcool package relates to each other would be helpful

trying to run new prisma setup. I am getting this error Booting local development cluster ! ▸ Recreating local_prisma-database_1 ... ▸ Starting prisma-db ... ▸ Recreating local_prisma-database_1 Starting prisma-db ... error ▸ ▸ ERROR: for prisma-db Cannot start service prisma-db: driver failed ▸ programming external connectivity on endpoint prisma-db ▸ (5359700751f218d9d8bba684036b0e63589593081095fcf52ff8a97750244e2d): Error ▸ starting userland proxy: Bind for 0.0.0.0:3306 failed: port is already Recreating local_prisma-database_1 ... done ▸ ▸ ERROR: for prisma-db Cannot start service prisma-db: driver failed ▸ programming external connectivity on endpoint prisma-db ▸ (5359700751f218d9d8bba684036b0e63589593081095fcf52ff8a97750244e2d): Error ▸ starting userland proxy: Bind for 0.0.0.0:3306 failed: port is already ▸ allocated ▸ Encountered errors while bringing up the project. ▸ Get in touch if you need help: https://www.graph.cool/forum To get more detailed output, run $ export DEBUG=“*” Creating stage dev for service mlaPrisma ! ▸ ‘ECONNRESET’: request to http://localhost:4466/cluster failed, ▸ reason: socket hang up Get in touch if you need help: https://www.graph.cool/forum To get more detailed output, run $ export DEBUG=“*”

I have previously mysql installed and using that port 3306

Any ideas how to fix this issue?

how can i reinsert the seed data? i can not find a seed command in the docs

anyoen know the fastest way to go from beta -> prisma?

@Nat @peter This was hidden in a thread somewhere: 1) Prisma - a GraphQL engine 2) graphql-yoga - a GraphQL Server that could use Prisma as a Backend 3) Graphcool Framework - a complete backend solution with a GraphQL interface, serverless functions and webhooks that will use Prisma as its Engine 4) Graphcool Cloud - a hosted version of the Graphcool Framework

But does GCF currently support Prisma as of 1.0? I assume yes?

@senorcodecat No it does not yet, but it is planned

You are very well dressed for a Slack profile pic.

But so am I

Ok. So looks like I'll continue to use GCF with Graphcool hosted cloud DB.

I’m working on adding auth to the prisma-react-fullstack-basic. I have the mutation set up for signup as: signup(email: String!, password: String!): AuthPayload! When I try it out in the playground this way: mutation { signup(email: “test@test.com” password: “password”) { token user { id } } } I get an error of: { “data”: null, “errors”: [ { “message”: “Cannot return null for non-nullable field Mutation.signup.“, “locations”: [ { “line”: 3, “column”: 3 } ], “path”: [ “signup” ] } ] } I think I added all the needed files and dependencies etc. and ran prisma deploy again. Everything shows up in the prisma.graphql I have to go, I’ll check back later to see if anyone had any ideas.

Hello everyone. I have a question. Can you tell me how can I access the prisma APIs from the frone-end directly? Now I can access the application APIs, following the examples. But I didn't find an example for accessing the prisma API.

@ehodges did you write the mutation and does it return something?

you have to generate a jwt

Thank you, @harmony

using

prisma-cli

my

database.graphql

doesn’t update… anyone experience this?

uhh

database.graphql

shouldn't update?