mistercrunch commented on issue #30761: URL: https://github.com/apache/superset/issues/30761#issuecomment-2465760730
All of our `docker compose` setups, including docker-compose-image-tag.yml, are NOT recommended for production use. From https://superset.apache.org/docs/installation/docker-compose/ <img width="1019" alt="Screenshot 2024-11-08 at 1 11 01 PM" src="https://github.com/user-attachments/assets/1bc13819-4cbf-47f9-a5ef-5f24204a66b0";> On top of what is described there, there was a challenge around segmentation while supporting dev AND prod use cases within docker-compose semantics, where there was a lot of conditionality in docker-compose (if dev then do_this else do_something_else) which could lead to confusion and security issues. Because of that we decided to recommend helm/k8s/minikube for prod use cases, where we can make sure all the conditions and configurations point to prod/secure images and configurations. -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
