You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After PR #1713 ("Support running superset via pex") the configuration variables SUPERSET_WORKERS, SUPERSET_WEBSERVER_ADDRESS, SUPERSET_WEBSERVER_PORT and SUPERSET_WEBSERVER_TIMEOUT are silently ignored, with the consequence that the webserver always tries to bind to port 8088 on all available interfaces (incidentally, the default is supposed to be 127.0.0.1 so I think there's something else going wrong, other than ignoring the config variables).
Launching superset with the appropriate command line parameters still works, but it's obviously cumbersome and risk-prone when multiple instances of superset run on the same server or if the server is shared with other services.
The text was updated successfully, but these errors were encountered:
After PR #1713 ("Support running superset via pex") the configuration variables SUPERSET_WORKERS, SUPERSET_WEBSERVER_ADDRESS, SUPERSET_WEBSERVER_PORT and SUPERSET_WEBSERVER_TIMEOUT are silently ignored, with the consequence that the webserver always tries to bind to port 8088 on all available interfaces (incidentally, the default is supposed to be 127.0.0.1 so I think there's something else going wrong, other than ignoring the config variables).
Launching superset with the appropriate command line parameters still works, but it's obviously cumbersome and risk-prone when multiple instances of superset run on the same server or if the server is shared with other services.
The text was updated successfully, but these errors were encountered: