-
Notifications
You must be signed in to change notification settings - Fork 2.8k
serve apis at a root other than / (close #1141) #1171
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
Conversation
|
Review app for commit c89d023 deployed to Heroku: https://hge-ci-pull-1171.herokuapp.com |
|
@rakeshkky, I set But if I go to |
|
@praveenweb Looks like the console is not respecting the prefix when generating the API url. |
|
Review app for commit d971da0 deployed to Heroku: https://hge-ci-pull-1171.herokuapp.com |
|
Awesome to see that this is on the way, as this issue is blocking our use of Hasura on a server with many projects on it! |
|
Review app for commit 1b71f3a deployed to Heroku: https://hge-ci-pull-1171.herokuapp.com |
karthikvt26
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to console code looks fine.
|
Review app for commit d6cf891 deployed to Heroku: https://hge-ci-pull-1171.herokuapp.com |
shahidhk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functionality is okay. Tested out by putting GraphQL Engine behind caddy.
@rakeshkky Resolve the conflicts and we can merge. @0x777 Awaiting your review.
Resolve Conflicts: server/src-exec/Main.hs server/src-lib/Hasura/Server/Init.hs
|
Review app for commit 3812d6d deployed to Heroku: https://hge-ci-pull-1171.herokuapp.com |
|
ref #1141 (comment) for more info |
|
closing this in favor of #1222 |
|
Review app https://hge-ci-pull-1171.herokuapp.com is deleted |
|
@0x777 having some option that allows us to set a As explained at this comment, whenever someone wants to expose hasura on a different path, we need to either get a load-balancer capable of trimming a prefix off the path or place an It seems that this was already done in this effort/PR, but it wasn't merged because the need for this was fixed by other PR. @0x777 Is there a plan to include an option on the graphql-server similar to this one? |
<!-- The PR description should answer 2 important questions: --> ### What Much in the vein of hasura/v3-engine#1166, we move the model aggregate planning from `sql` to the `plan` crate. No tests actually exercise this code in the OpenDD IR pipeline yet, perhaps if we extend the GraphQL -> OpenDD IR pipeline we can put it under test. ### How Move the code, fix the errors. Functional no-op. V3_GIT_ORIGIN_REV_ID: 7beee0aec828296fefa24c975d4662a20aa0d2e5
Description
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
close #1141
Solution and Design
Allow server APIs and console to be served at a path other than
/configurable via
--url-rootcommand line flag andHASURA_GRAPHQL_URL_ROOTenvironment variableType
Checklist: