-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Webapp: Could you please provide configurable base url? #8167
Comments
+1! |
Any update on this? I need this as well, and it may block my use of Airbyte completely. I see a PUBLIC_URL variable in airbyte-webapp/public/index.html, but it looks like this is a build-time variable, and not something we can set at deploy time. Is that correct? Is there any way to accomplish this base url configuration when deploying via Helm chart? |
Hey, @abaerptc had a word with the frontend team and it looks like we are currently not finding the bandwidth to get this up on the roadmap. I will follow up later in a couple of weeks and see if we can pick it up. |
* add `<base>` tag in index.html through nginx filter * add basename configuration of react-router-dom BrowserRouter element * modify `url()`s in index.css to use relative paths * modify `fetch()`ing buildInfo.json to use relative url * change vite configuration to use relative base * add `BASE_URL` env variable * add `webapp.baseUrl` helm value
Please make this work |
Any update on this? It's such an integral issue and a blocker to even start using Airbyte properly. Is there anything we can do to move this forward? |
any update here ? |
is there a solution yet ? |
Would help a lot... |
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte. |
This issue was closed because it has been inactive for 20 days since being marked as stale. |
Can we re-open this issue? This is an important feature that is currently blocking us from using Airbyte. |
I second this. We would like to use Airbyte at our organization but are blocked due to the base url not being configurable. |
We still need a solution here. Its still not working on base urls. please reopen |
same we are trying to use but Base URL is not configurable any hack ? |
I have recreated the same issue , hope this will get resolved . |
Tell us about the problem you're trying to solve
I deployed airbyte on K8s. Instead of
kubectl port-forward
, I used ingress and istio virtual service to make a url for airbyte webapp, likehttps://example.com/base/path/
.But it seems that airbyte webapp always assumes it is located at the root
/
, and I cannot find how to configure the webapp so that it knows its base url is/base/path/
.Describe the solution you’d like
Make base url configurable.
Describe the alternative you’ve considered or used
None.
Additional context
None.
Are you willing to submit a PR?
Sorry I'm not a frontend developer...
The text was updated successfully, but these errors were encountered: