click on "Configure auth providers"

then you have to enter your Auth0 api key etc.

💥

that’ll be it. cheers!

🎉

hi @nilan, yes, the email provider would be really ok, but i would and i am using the auth0 login interface and when i sign up i create the user on auth0 but how can i create the user on graphcool too? is there a specific callback that i have to use from the auth0 service, so i can trigger the createUser mutation in case i just signed up?

Have you seen this guide? https://graph.cool/docs/guides/react-apollo-auth0-lock Should be exactly what you need 🙂

you can also check the hosted example @sunrising http://apollo-auth0.netlify.com/ 🙂

Welcome @presto 🙂

thank you nilan, i will let you know if i will succeed

thanks.

Hey guys, i am trying graphcool, i am doing the on boarding tutorial, but when i click in the

react-relay

link to download the sample app, i am getting a 502

Hey @presto. I’ll look into it right away! 🙂

Thanks for letting us know!

cool, np

Should be fixed now @presto 🙂

👍

So I just discovered GraphCool. What I like about it is that building the data layer seems to be as simple as defining the GraphQL schema. Changing that schema involves no DB migration. Wow. That really does sound good (if I'm not making stuff up here based on my still cursory understanding of GraphCool) But the one thing I'm not sure about is what is the backing db technology? Is it a distributed graph db, nosql, sql or something else? How do I know that behind the scenes there exists an efficient implementation (with the net result of my GraphL queries being least costly and performant at scale) ... Can someone enlighten me about how GraphCool solved db optimization?

"Hi" I should add

🙂

Is it using something like https://github.com/stems/join-monster ?

hey is there a #learnapollo channel? I’m getting some unmet peerdependency warnings trying the exponent example

after I

yarn add apollo-client react-apollo

@schickling ^^

hey @monkeybonkey, does the app still work regardless of the unmet peer dep? if not you can try to have a look at the versions used for apollo and react-apollo by checking the package.json in one of the solution folders. I think apollo version 0.6 is pretty new, you might have more luck with 0.5.26

hey @marcfawzi, welcome :) your observation is accurate in that you only have to define models, fields and relations so we can automatically generate your schema. your data is stored using AWS Aurora which is a highly-scalable MySQL variant. as we are using Sangria rather than graphql-js to spin up your GraphQL backend, we make use of a feature called deferred resolving to reduce the amount of db queries significantly for nested queries. And of course we employ similar means to what join-monster does to be smart about the db queries we do execute. another dimension is scaling the number of instances, again relying on different services offered by AWS. Hope that helps! if you have more specific questions or requirements I'm happy to chat more about that :)

@nilan yes it still works - just makes me a bit uncomfortable ignoring warnings 🙂 - I downgraded the apollo-client to 0.6 from 0.7 since that’s what react-apollo wanted and that seems ok, however it still has the unmet react-dom peer dependency. It seems to run without error however. I’ll test the graphql queries some and see if it breaks anywhere

alright, cool! Would be great if you can create a new issue containing the information resulting from your research: https://github.com/learnapollo/learnapollo/issues

in the graphcool data explorer how do I enter a value into the json data field - it doesn’t seem to keep my edits and sometimes it won’t let me focus away from the field