Jim
06/16/2018, 12:47 PMthisismissem
06/16/2018, 2:22 PMthisismissem
06/16/2018, 2:27 PMuser
06/16/2018, 5:10 PMeugenistoc
06/16/2018, 6:30 PMprisma deploy
deploy there? Where do all of the tutorials fit in with the prisma cloud service? What are the servers for in prisma cloud? Do I need to add my own? Can I use docker with prisma cloud? Should I use docker at all? what about node-basic
and node-advanced
?
It seems there is a whole lot of background knowledge that is assumed in so much of this ecosystem. I’m yet to experience the simplicity advertised on the homepage of prisma.io. Its just all very confusing, imo.Dan Ryan
06/16/2018, 9:00 PMDan Ryan
06/16/2018, 9:01 PMVimox
06/17/2018, 9:52 AMAvi Block
06/17/2018, 3:23 PMBinding
(where I differ is that I'm getting my schema by converting the downloaded introspection result json to SDL with buildClientSchema + printSchema)
then I call npx graphql-binding --language typescript --input schema.ts --outputBinding binding.ts
and get
TypeError: this.schema.getQueryType is not a function
at TypescriptGenerator.renderQueries (node_modules/graphql-binding/src/codegen/TypescriptGenerator.ts:180:35)
at TypescriptGenerator.render (node_modules/graphql-binding/src/codegen/TypescriptGenerator.ts:144:31)
at node_modules/graphql-binding/src/bin.ts:58:34
at step (node_modules/graphql-binding/dist/bin.js:41:23)
at Object.next (node_modules/graphql-binding/dist/bin.js:22:53)
at node_modules/graphql-binding/dist/bin.js:16:71
at Promise (<anonymous>)
at __awaiter (node_modules/graphql-binding/dist/bin.js:12:12)
at run (node_modules/graphql-binding/dist/bin.js:81:12)
at Object.<anonymous> (node_modules/graphql-binding/src/bin.ts:40:1)
Avi Block
06/17/2018, 3:46 PMAvi Block
06/17/2018, 3:47 PMKien Vo
06/17/2018, 7:18 PMcloudSession
is stored in ~/.prisma/config.yml. If I want to login to another Prisma account, I have to remove that cloudSession
and do the CLI: prisma login
again. @nilanjoar
06/17/2018, 11:46 PMRafael Rozon
06/18/2018, 3:42 AMprisma init
, copied the docker-compose file to the database folder, removed the endpoint key, ran prisma init and then got a new endpoint key in the prisma.yml file. I ran docker-compose up -d
and it was fine, then when I ran prisma deploy I get this: Error: Could not connect to server at <http://localhost:4466>. Please check if your server is running.
. Am I missing anything? For what I understand I need 2 servers, the one created by docker-compose which is where Prisma sits, and then the web server to consume it.Moritz
06/18/2018, 8:31 AMapollo-client
, the first time I subscribe, everthing works as expected. However, when I reload my frontend and resubscribe, the subscriptions dont get fired any more. Now, how does prisma handle resubscriptions, and what happens to the old subscriptions when my client app is killed and relaunches, i.e. the subscription is left hanging and another subscription is called from the same client? I know that this is deeply linked with apollo and the solution is probably located on the client side, however, I still thought I'd ask what happens on the server side. Glad about any input and experiences! Thanks!hamdi
06/18/2018, 9:53 AMeelke
06/18/2018, 9:53 AMeelke
06/18/2018, 9:54 AMeelke
06/18/2018, 9:56 AMeelke
06/18/2018, 9:56 AMeelke
06/18/2018, 9:58 AMdohomi
06/18/2018, 1:50 PMdohomi
06/18/2018, 1:50 PMdohomi
06/18/2018, 1:50 PMdohomi
06/18/2018, 1:52 PMdohomi
06/18/2018, 1:57 PMmop
06/18/2018, 2:11 PMmop
06/18/2018, 2:12 PMmop
06/18/2018, 2:26 PMmullinb
06/18/2018, 3:34 PM