komoot / superset-reverse-nginx-example

a small working example of using superset with a base url using nginx' reverse proxy

This is a working example based on various sources to have superset running behind a base url using nginx.

It is a common requirement to have superset running under a base url, (https://mydomain.at/analytics/ instead of https://mydomain.at/). There had been multiple issues and discussions around it (1 2 3 4). Still it was not crystal clear how to put all elements together. To save some time for others, we compiled a working example in this repository.

Resources

• apache/superset#1866 (comment)
• https://github.com/amancevice/docker-superset/blob/master/examples/postgres/docker-compose.yml
• https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/

How to run

• docker-compose up -d --build
• docker-compose down -v

superset-reverse-nginx-example's Issues

nginx.conf does not work anymore with Superset update

Hi,
I've been using this nginx configuration over superset until last week, but after updating Superset it does not work anymore, and it seems superset gets /analytics path now and returns 404.
thanks

Proxy pass for node server

can we integrate superset webpack builds? in superset

Different port than port 80 for reverse-proxy server .

Hey, So I am trying to host superset behind a proxy server running on port 8080. However, redirects by the reverse proxy are just ip rather than being ip:port.

Example: Suppose the IP of the server is 192.168.43.23 and reverse proxy is hosted on port 8080. I opened an incognito window and tried to open http://192.168.43.23:8080/analytics/superset/welcome. Then the login redirect goes to http://192.168.43.23/analytics/login/ instead of going to http://192.168.43.23:8080/analytics/login/.

Same thing happens if I use curl or wget.

How do I resolve this?