mistercrunch commented on PR #33137:
URL: https://github.com/apache/superset/pull/33137#issuecomment-2811060113
Few thoughts:
- Docker Compose should probably come first as the easiest way to trial
Superset and what we generally recommend to get started quickly and for dev,
can be easily used to kick start various versions. Caveat - not intended for
production
- For K8s, maybe mentioning Helm and minikube — I think that’s what most
people will want for a prod set up. Could mention @villebro ' k8s operator SIP
and link to it
- pip is rough. wouldn't recommend to anyone personally, fine to mention it,
but docs are incomplete/dated, but can be used as a cookbook to fine tune other
methods
Would be nice to add a quick comparison table across methods (use case,
pros/cons). Let me try to get gpt to give it a shot.
| Method | Best For | Pros
| Cons
|
|------------------|-------------------------|---------------------------------------------------|------------------------------------------------------------|
| Docker Compose | Trial + Dev | Quickstart, self-contained,
flexible | Not production-ready, limited scalability |
| Helm + K8s | Production | Scalable, widely adopted,
community-supported | Requires K8s knowledge, more setup involved
|
| pip | Custom setups / hacking | Lightweight, flexible, good
for contributors | Dated docs, missing pieces (Redis, Celery, etc),
fragile |
--
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]
