Ability to set base path for the front-end

[maxim-kukushkin]

Is your feature request related to a problem? Please describe. Having a separate subdomain per service is not always a solution. Some people may have limited SSL certificate availability, for others it's harder to write URLs in the app (you can't refer to a relative subdomain, but can redirect to a relative path), sometimes (like me) it's because you need to hide multiple apps behind a single web-server.

Currently it's not possible to make Zigbee2MQTT's frontend available in a subpath of a server, because all links point to absolute paths starting from root

Describe the solution you'd like A configuration parameter that sets the base path (prefix) to be used for all requests and links.

For example: url_base_path: zigbee2mqtt/

Then instead of "https://example.com/assets/index.1a2b4112.js" the app accesses "https://example.com/zigbee2mqtt/assets/index.1a2b4112.js"

Describe alternatives you've considered I've tried using ProxyPass/ReverseProxyPass of Apache Web Server, but it doesn't seem to help

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[maxim-kukushkin]

No, it's not stale it's important

[hedefalk]

I thought this was what frontend.url in settings would be for. Is it not just a matter of settings:

<base href="https://example.com/zigbee2mqtt"></base>

in the html doc?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[maxim-kukushkin]

I thought this was what frontend.url in settings would be for. Is it not just a matter of settings:

<base href="https://example.com/zigbee2mqtt"></base>

in the html doc?

I can't see this setting. It seems like zigbee2mqtt uses a Yaml configuration file, while the above syntax is XML Do you by any chance have a link?

btw, the base url setting above includes the domain, which might not be convenient. The original request is simply to add support of path prefix. So that for example instead of referring to / link would refer to /foo/bar/. That would be domain-agonstic

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[maxim-kukushkin]

not stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[maxim-kukushkin]

Sigh... not stale

I wish this useless bot would nudge the maintainers instead, to come and close the ticket themselves if they find necessary. Lack of response from maintainers doesn't make something stale