alexleach commented on issue #985: URL: https://github.com/apache/superset/issues/985#issuecomment-902920847
Just landed on this having been looking for a way to configure a base url path. Like others, I was hoping to find an easy and supported way of configuring the superset base url. With docker-compose being the first documented way to launch superset, I'd have thought there would be good options! I tend to proxy my containers through traefik, using a `PathPrefix` directive, which map to a base url configuration option. By using base urls instead of subdomains allows me to use a single SSL certificate on the traefik proxy to host a number of web apps and services. Requiring separate subdomains means more SSL certificate requests and renewals, which is a bit of a chore, so I'd far prefer to route requests based on base urls than on subdomains. I checked out the [superset-reverse-nginx-example](https://github.com/komoot/superset-reverse-nginx-example), in traefik that would be a lot of `PathPrefix` options to configure! It would be possible of course, but really not ideal! From the above comments, it looks like the js is currently limiting a configurable base url, in that the js hosts most of the hard-coded URLs. Is this still the case? Does anyone know if there is a way to rebuild the repo from typescript with a configurable base url? e.g. PR https://github.com/apache/superset/pull/15105 -- 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]
