https://www.prisma.io/ logo
Join Slack
Powered by
Once rebooted, the local target is longer recognis...
# prisma-whats-new
v
Once rebooted, the local target is longer recognised when I do a local deploy, e.g.
Copy code
No service with id 'cj9ttwnlb009h0150kg59sgb0' in account <mailto:test@test.org|test@test.org>. Please check if you are logged in to the right
 ▸    account.
What’s right way to approach this? It is only removing the local target from 
.graphcoolrc
?
a
Does that happen every time? Because the volumes for the docker container should be persisted...
v
I’ll try to replicate — might’ve actually happened after I destroyed the containers with everything related
a
If it was deliberate, then removing the target from 
.graphcoolrc
was indeed the missing step
v
but it raises the question anyway: if I am sharing the project with other devs, and they checkout my repo and try to deploy the project for the first time, they’ll get the issue anyway. Does that mean 
.graphcoolrc
should not be checked into a repo when developing collaboratively?
a
.graphcoolrc
should generally not be under source control
But... I still think there can be some improvement.
Shared cluster environments are 'supposed to exist' for the second dev, and local environments shouldn't
So maybe there could be an option to just create a new service if it isn't found for local only
I'll create a proposal for it on Github
https://github.com/graphcool/framework/issues/1285 Please share your thoughts and experiences 😄
v
Ta. I’ll have a look now.
👍🏻 1
2 Views
Open in Slack
PreviousNext
Powered by