zcaudate
11/02/2017, 11:08 PMKat
11/02/2017, 11:09 PMKat
11/02/2017, 11:09 PMKat
11/02/2017, 11:09 PMagartha
11/02/2017, 11:10 PMagartha
11/02/2017, 11:10 PMTavo
11/03/2017, 12:09 AMagartha
11/03/2017, 12:09 AMTavo
11/03/2017, 12:11 AMTavo
11/03/2017, 12:14 AMagartha
11/03/2017, 12:15 AMagartha
11/03/2017, 12:16 AMzcaudate
11/03/2017, 2:12 AMzcaudate
11/03/2017, 2:13 AMrhishikeshj
11/04/2017, 5:44 AMrhishikeshj
11/04/2017, 5:44 AMTavo
11/04/2017, 3:46 PMinvoke-local
look into thatrhishikeshj
11/06/2017, 8:10 AMrhishikeshj
11/06/2017, 8:12 AMgraphcool init && graphcool local up && graphcool deploy
This ultimately deploys the graphcool services locally and you can launch a playground against it. What I was doing was starting from a project which was exported from the Graph.cool console in the browser. Maybe there’s an extra step involved when deploying exported projects locallyrhishikeshj
11/08/2017, 6:14 AM<project-id> was not added to the <mailto:test@test.org|test@test.org> account
Kat
11/08/2017, 6:34 AMKat
11/08/2017, 6:34 AMrhishikeshj
11/08/2017, 7:03 AMzcaudate
11/08/2017, 11:17 AMzcaudate
11/08/2017, 12:39 PM