maudrid opened a new issue, #24823: URL: https://github.com/apache/superset/issues/24823
## [SIP] Proposal to allow Superset to run in a sub path URL ### Motivation At our company we host our application for customers with Superset as part of the service. We have a URL scheme as follows: `https://<customer-name>.<service-domain>.com` For each customer we now have 2 domains because we also need `https://superset.<customer-name>.<service-domain>.com` as well as the afore mentioned one, since Superset only runs successfully on the root. We also cannot use a wildcard domain certificate like `*.service-domain.com `because wildcard certificates do not work on sub-sub domains. So now we have to create additional domain certificates for each customer. ### Proposed Change It would be great if we can run superset behind a reverse proxy on a sub path. For example: `https://<customer-name>.<service-domain>.com/superset` Some configuration options to enable this behaviour would be required: Grafana, for example, has these options: ``` serve_from_sub_path = true root_url = https://<customer-name>.<service-domain>.com/superset ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
