Running Dgraph locally in Docker the schema took several minutes to load to a done state. So my next step was to take everything and cast it out on the net doing so on AWS with a single host setup following the deploy docs.
I can load a very simple schema no problem, but when I try to load my lengthy schema the server errors out and by watching Ratel connection indicators it seems to cycle booting up and then going offline until it seems to finally just quit.
I thought that maybe it was my setup so I used my invite to slash.graphql and uploaded my schema there. After submitting it, there was no indication anything was happening. After a few minutes I got a brief error that was quickly followed by a generic server error. Sorry, I couldn’t quite get what the first error said.
During writing this, I went and tried to submit the same schema again on slash.graphql and it accepted it almost immediately and took me to the API explorer.
I am still unable to get a response from my own AWS running instance.
Error fetching schema from server: Please retry again, server is not ready to accept requests
Although I can see it on: http://126.96.36.199:8080/
Dgraph browser is available for running separately using the dgraph-ratel binary
The /graphql endpoint is not providing the schema when trying to connect to it with GraphQLPlayground still.
Should I piece apart my schema and send it in increments/updates? It seems that the algorithm for parsing the schema only updates the fields that have changed, so that might be the best way to get it all on a server is incrementally instead of all at once.
I would post the schema but it was too large to allow in this post But you can see it where slash.graphql finally processed it: https://primo-yam-7925.us-west-2.aws.cloud.dgraph.io/graphql