[6.0.0rc2] Custom prefix for URL on your site, not localhost. Closing port 8088 to external access.

[KirP32]

Is there anyone who uses Apache Superset on their site with a custom path, for example: mysite.com/analytic/monitor

I'm running superset in docker, checkpoint 6.0.0rc2 (to change SUPERSET_APP_ROOT). The problem is that when I remove port 8088 from docker, I can't reach the apache superset container. If you create a custom network using:

networks:
  infra_net:
    external: true

and assign it to superset:

services:
  superset:
    container_name: superset_app
    networks:
      - infra_net

Then superset will complain that it cannot connect to the database. You can try to fix this through custom SQLALCHEMY_DATABASE_URI, however, after starting the container, it does not work. Has anyone had similar problems?

[dosubot[bot]]

Yes, you can run Superset with a custom URL path prefix by setting the SUPERSET_APP_ROOT environment variable (for example, SUPERSET_APP_ROOT=/analytic/monitor). This allows Superset to be served under a custom path like mysite.com/analytic/monitor, and login redirects will work correctly with the prefix source.

When closing port 8088 to external access, Superset should be exposed via a reverse proxy (such as Nginx or Traefik) that forwards requests to the container internally. Make sure to enable proxy header handling in Superset using ENABLE_PROXY_FIX and configure PROXY_FIX_CONFIG for proper path and header forwarding source.

For Docker networking: if Superset cannot connect to the database after moving to a custom network, check that the database hostname in SQLALCHEMY_DATABASE_URI is resolvable from the Superset container within that network. Avoid using localhost for the database host; instead, use the service name defined in your Docker Compose file, host.docker.internal (Mac/Windows), or the Docker gateway IP (Linux) source.

Superset's default Docker Compose setup is for single-host development and may require extra configuration for production, especially with custom networks and reverse proxies. If you need more advanced networking, ensure all services are on the same Docker network and that service names are used for connectivity source.

Let me know if you need more details on reverse proxy configuration or troubleshooting database connectivity!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}