-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Can't serve from a subpath #529
Comments
I acknowledge the problem. |
It is absolutely not my domain either, but I found this issue where there are a lot of comments about this feature : storybookjs/storybook#1291 I hope that could help. |
As helm-dashboard is built in a However, if helm-dashboard is built in a default I know my idea is a big change, but can it be a possible solution ? |
I understand your idea, but it's same effort as making it work from subdirectory IMO. I'd prefer to keep it elegant. |
I too would want to serve the dashboard from a subpath. As things stand an ingress definition can send traffic to the service, but assets (and hence the dashboard itself) won't load. [1] https://create-react-app.dev/docs/deployment/#building-for-relative-paths |
@r-maerz If you are proficient in ReactJS, it would be great if you bring the PR that would improve the code with this capability |
Description
The helm-dashboard seems to only respond on a
/
context.I want helm-dashboard to respond from my.domain.com/helm-dashboard.
Screenshots
Additional information
As stated in the ingress-nginx documentation, I deployed helm-dashboard like this :
Here is the result of the Ingress object deployed :
Subsequently, I would like to set up oauth2 authentification.
The text was updated successfully, but these errors were encountered: