So, running graphcool login --token <mytoken&gt...
# prisma-whats-new
v
So, running graphcool login --token <mytoken> and the CLI is stuck on “Authenticating…” — what could I be doing wrong?
n
what's your
graphcool version
?
v
graphcool/0.8.5 (linux-x64) node-v8.2.0
it’s running in a VM
d
Are you running docker native (aka linux directly, docker for mac, docker for windows) or docker toolbox?
Should have looked closer, you’re on linux it seems.
v
Linux, yes
d
Is this working for you?
curl '<http://127.0.0.1:60000/system>' -H 'Content-Type: application/json' -d '{"query":"mutation {authenticateCustomer(input:{auth0IdToken:\"MuchTokenSuchMasterWow\"}){token, user{id}}}"}' -sS
v
Apparently not 🙂
curl: (7) Failed to connect to 127.0.0.1 port 60000: Connection refused
I guess I have something missing
d
docker ps
and verify that the port and host are correct for the curl
v
Strange, it says the daemon isn’t running … I was sure it was
hold on
d
Not having any Graphcool running could indeed be an issue 🙂 Strange however that the CLI doesn’t catch that.
v
Yeah — I need to figure out what’s wrong with my docker
it’s up and running and yet it doesn’t work
thanks anyway, at least I am going somewhere
d
👍
v
Right, since I am really to all this, let me take a step back.
I’ve started a project online. Question #1: can I actually “checkout” the project locally?
I was thinking “i’ll authenticate, then pull”
but I understand now auth wants a graphql running in a docker locally?
d
As far as I understand your question: You can upgrade a project to the CLI workflow, download the sources, then start developing locally and using Git. You don’t necessarily need a local docker setup, you can just deploy to the live version.
v
I see — so essentially I need to upgrade to a paid project in order to get it locally, correcT?
n
no, upgrade in the sense of upgrading the legacy project to the framework
it's not required to be on a paid plan for the local workflow
v
I see! Thanks.