Yes I've been trying to deploy using helm charts, and I've exposed my frontend service at mydomain.com/signoz, when I try to load it, I see frontend still tries to load some assets at base route from my domain (mydomain.com/assets, whereas these are available at mydomain.com/signoz/assets).
Describe the solution you'd like
Ideally if we can have some configVars or env for frontend service in override-values.yaml, that would be great something like frontend.env[0].name = 'FRONTEND_PATH', frontend.env[0].value = 'basePath'
Describe alternatives you've considered
If this is not possible then I'll probably create a subdomain and setup signoz there at root.
Is your feature request related to a problem?
Yes I've been trying to deploy using helm charts, and I've exposed my frontend service at mydomain.com/signoz, when I try to load it, I see frontend still tries to load some assets at base route from my domain (mydomain.com/assets, whereas these are available at mydomain.com/signoz/assets).
Describe the solution you'd like
Ideally if we can have some configVars or env for frontend service in override-values.yaml, that would be great something like frontend.env[0].name = 'FRONTEND_PATH', frontend.env[0].value = 'basePath'
Describe alternatives you've considered
If this is not possible then I'll probably create a subdomain and setup signoz there at root.