Hello. When deploying Airbyte via Helm chart, is there a way to configure the root path? For example, if I have the webapp service deployed at my-url/airbyte, and I need it to look for resources with paths like my-url/airbyte/index.css rather than my-url/index.css, how do I configure that?

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2941 to ensure timely resolution!

Hey could you explain your usecase more? Like probably how is that gonna help for your problem? Also for further assistance you can post at discuss.airbyte.io

@Harshith (Airbyte) I found this issue which is the same request and explains it better than I can: https://github.com/airbytehq/airbyte/issues/8167

Hey I have seen the comment on the Issue. Team will get back to you soon

@Harshith (Airbyte) Any update on this?

I don't think team got the time to check it. Could you help with more detailed usecase maybe I will see if we can hack something to make it work for you.

I need to be able to deploy airbyte at a non-root path, for example, http://my-url.com/airbyte, rather than at the root path, http://my-url.com. However, when I do that, I get errors because the webapp is looking for resources at http://my-url.com/index.css, so I need a way to configure it to correctly find them at their actual location, http://my-url.com/airbyte/index.css.

Hey, sorry for this. I am checking with team if there is a quick way to solve it? Will get back

Hey @Ashley Baer, thanks for the question and sorry for the delay. Just wanted to provide an update on this: It looks like this issue is currently on the frontend team’s backlog and out of bandwidth at the moment. Let us know if there’s anything we can do and if yoo are still experiencing this issue