-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
proxy all requests from console through cli #1440
Labels
c/cli
Related to CLI
c/console
Related to console
e/intermediate
can be wrapped up in a week
p/medium
non-urgent issues/features that are candidates for being included in one of the upcoming sprints
s/wip
Status: This issue is a work in progress
Comments
Very handy in dockerized dev environments where the ui and cli see different addresses for the graphql-engine. This change would make it so the host browser only needs to care about 1 of those addresses. |
cc: @danielcompton |
hasura console --endpoint http://graphql-engine:8080 --address 0.0.0.0 --console-port 8080 --api-port 8081 --api-external-host https://my-hasura-cli-host.com |
Closed in favor of #2824 which will allow running CLI on docker containers or elsewhere. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
c/cli
Related to CLI
c/console
Related to console
e/intermediate
can be wrapped up in a week
p/medium
non-urgent issues/features that are candidates for being included in one of the upcoming sprints
s/wip
Status: This issue is a work in progress
For CLI hosted console, only migration requests are procured through CLI. To host this console on a server, all requests should go through CLI protected by the access key.
The text was updated successfully, but these errors were encountered: