mistercrunch commented on issue #32178: URL: https://github.com/apache/superset/issues/32178#issuecomment-2655219739
Reading through the config, I'm realizing that the intent in the setup is [probably] to use 80 since that's where nginx is configured. Apparently it manages reverse-proxying `/ws` to the websocket server. Personally been using 8088 and 9000 now, but seems there's an opportunity to clean all this up with a single entry port that would provide consistency across various setups. I'm not sure how I feel about taking over `80` (like nginx does currently) for dev, clearly you don't want for different pieces of software fighting for `80` Now realizing that nginx.conf is only used for docker-compose.yml, so it's easy to proxy to 9000 and shouldn't break other things, but will require people to point to the nginx port not superset_app (flask). Anyhow lots of options/tradeoffs here. Maybe the best idea is to always use `8088` across all docker-compose.*, would require: - running the flask app on another port - configuring nginx to run on 8088 - routing nginx to 9000 on main docker-compose.yml file - breaking things for anyone running on `80` now -- 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]
