-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traefik error #118
Comments
Traefik work, cassandra-data-apis not resolv ` <script>window.addEventListener('load', function (event) {
|
From the log messages, it looks like you don't have a keyspace created in your database. You need at least a user-defined keyspace in your database for the service to expose it. I'm not sure I follow the issue related to the playground. If you are able to access the graphql playground, the playground will default to |
The graphql-playground can fail because of CORs (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors). After #119 is merged you can use the following configuration to access from any IP address.
|
For me as a non-programmer, this is a problem. In the future, already with the help of convenient and familiar tools for using graphql, I would have continued my work. |
Sure, we are here to make the project as easy to use as possible, I've filed #121 to make sure the behaviour is clear. |
I create config.
{"level":"info","ts":1588522561.0406232,"caller":"log/logger.go:74","msg":"using config file","file":"/root/config.yaml"}, {"level":"info","ts":1588522561.2010622,"caller":"log/logger.go:74","msg":"building schemas"}, {"level":"info","ts":1588522561.2910392,"caller":"log/logger.go:74","msg":"get started by visiting the GraphQL playground","url":"http://localhost:8080/graphql-playground"}, {"level":"info","ts":1588522561.2911048,"caller":"log/logger.go:74","msg":"server listening","port":8080,"type":"GraphQL"},
curl http://192.168.16.5:8080/graphql-playground work
But https://DOMAIN/graphql-playground
Error 504
Gateway time-out
The text was updated successfully, but these errors were encountered: