You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the v3 engine doesn't support hosting it's own console? ddn console --local opens in a browser: https://console.hasura.io/local?url=http://localhost:3280&promptQLUrl=
But console.hasura.io/local is not a PWA either, so I'm not able to use it locally without consistent internet access. (And hasura.io also happened to have some downtime shortly before I submitted this issue. 😅)
Could the console either:
Support offline usage via PWA, or
Let ddn console --local host a local, static build of the console?
I'd certainly prefer the 2nd option, but I understand the PWA route if e.g. Hasura plans to keep the console closed-source.
The text was updated successfully, but these errors were encountered:
@bitjson the v3-engine container already ships the Graphiql playground. You can browse http://localhost:3280 to run GraphQL queries locally. Other features such as model explorer and observability are exclusive to the Hasura DDN cloud only. They require an internet connection to get data from Hasura cloud services.
However, there are alternatives if you want to view Traces and metrics locally. for example, add Jaeger container to the docker-compose file and modify the otel-collector.yaml config to export traces to Jaeger.
It looks like the v3 engine doesn't support hosting it's own console?
ddn console --local
opens in a browser:https://console.hasura.io/local?url=http://localhost:3280&promptQLUrl=
But
console.hasura.io/local
is not a PWA either, so I'm not able to use it locally without consistent internet access. (Andhasura.io
also happened to have some downtime shortly before I submitted this issue. 😅)Could the console either:
ddn console --local
host a local, static build of the console?I'd certainly prefer the 2nd option, but I understand the PWA route if e.g. Hasura plans to keep the console closed-source.
The text was updated successfully, but these errors were encountered: