Graphcool has a feature called $>graphcool local eject , which provides us with a docker-compose.yml file.
Now lets say, I go to production with that docker-compose.yml file, add my docker image for node graphql microservice to that as well. And now everything runs fine.
Next Release, I introduce some fields or introduce a new type, and now I want to do data migration on graphcool docker image.
How do I do it? Does Graphcool Service (docker based) has end points for me to push a new graphql schema to that? Can Graphcool still connect to exported setup of graphcool?
Issue by rohitghatol Wednesday Jan 10, 2018 at 07:36 GMT Originally opened as https://github.com/graphcool/prisma/issues/1568
Graphcool has a feature called $>graphcool local eject , which provides us with a docker-compose.yml file.
Now lets say, I go to production with that docker-compose.yml file, add my docker image for node graphql microservice to that as well. And now everything runs fine.
Next Release, I introduce some fields or introduce a new type, and now I want to do data migration on graphcool docker image.
How do I do it? Does Graphcool Service (docker based) has end points for me to push a new graphql schema to that? Can Graphcool still connect to exported setup of graphcool?