but if I already have it connected to a graph.cool...
# prisma-whats-new
w
but if I already have it connected to a graph.cool, how do I switch that?
e
you can change the target you’re using
w
how?
n
the local version is not connected to the Console, but you can connect the Playground to it
e
in your
.graphcoolrc
file you can configure where your targets point
e.g.
Copy code
targets:
  default: local
  local: local/cjaa6dfq200040156iex70hm5
  dev: shared-us-west-2/cjc0x9ppm1sz901712l6hqsq7
  prod: shared-us-west-2/cjc2gxsyx04al0117c3kfkas1
w
ah - How do I add a new one?
it only shows the remote one
e
just make a new target called whatever you want and point it towards a value of
local
inside your
.graphcoolrc
file
if you don’t have that file, you can just create one
w
where do I find that number? cjaa6dfq200040156iex70hm5
e
ah…
just try doing
local up
first
w
I did that
e
now do graphcool deploy --target local
or
rather
set your default to local
default: local
and just do
graphcool deploy
w
I did that
e
and it’s not working ?
w
where do I create the GUID for the local version
e
I just recall it was created automatically somehow
@nilan any insight? I can’t remember how the guid originally showed up lol
w
😄
n
could you try removing your auth credentials in
~/.graphcool
or
~/.graphcoolrc
and do
graphcool auth
or
graphcool login
again?
w
what they are called? cluster secret?
ah got it - okay I re-authed
now what
n
also, did you change your
NODE_ENV
?
w
no
n
now try deploying again as @elmir described
w
same error
where do I get the GUID from?
n
how does your
.graphcoolrc
look like?
your local one
w
n
I mean the one in the directory you're working in
w
Copy code
targets:
  prod: shared-eu-west-1/cjctbkp4o02fh0105aff50ccn
  local: local/wtfbbq
  default: local
n
please remove the line saying
local: local/wtfbbq
😄 and put
default: prod
. then do
graphcool deploy --target local
again
w
there we go - thank you
n
cheers 🙂
w
so is playground included in this? or do I need to install that too
oh it’s a desktop app
n
when visiting the local endpoint you should see a playground
in your browser
yea, it's also available as separate app
w
The requested resource could not be found.
n
when deploying you should have received an url like this
localhost:60000/simple/v1/cjbgdbfd000040186nh2z8c9s/
w
oh yah that did it
okay hopefully that’s it - thanks again
👌 1