One point to notice. None of Dgraph’s clients are made to run GraphQL(maybe in the future we could have one, but there are out there really good ones). Feels like you wanna do DQL queries and transactions. Following this docs Advanced Queries with DQL - Dgraphcloud, it shows that is possible to do with cURL. Therefore it is perfectly capable of being used in the Py client (for DQL).
I believe that any Dgraph service doesn’t expose that port. Not sure, I think that all will run at 80.
@docs and @gja - This docs feels odd. It opens a connection in the GraphQL subpath. Which confuses me.
client_stub = pydgraph.DgraphClientStub.from_slash_endpoint("https://frozen-mango-42.eu-central-1.aws.cloud.dgraph.io/graphql", "<api-key>")
Why a DQL query would run in a GraphQL subpath? The previous part of the docs mention that we have /query, /graphql, /mutate and /commit endpoints.
Also in the Ratel part mention that it should connect to the /graphql subpath. This would make the user think that Ratel supports GraphQL.