nytai commented on issue #9880: URL: https://github.com/apache/superset/issues/9880#issuecomment-779491988
The published docker containers already include the compiled resources. docker-compose volume mounts the repo and sets things up for development purposes, hence why the compilation step is necessary. We could add a version of docker-compose without volume mounts for quickly testing the app out, however that should ideally not be used in prod. The helm chart is also a great way to set up the app quickly for testing but it’s also not ideal for large scale prod deployments as it relies on containerized instances of redis and Postgres. It also expects knowledge of helm charts (most config usually happens in `values.yaml`) As far as prod deployments, there are so many ways to run a flask app, celery app, celery beat app, provide a database, redis instance, etc. that documenting each would be a huge task. We could point to other resources for deploying flask/celery apps though ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
