Hacker News new | ask | show | jobs
by jlkuester7 480 days ago
Yeah, was thinking that as well. IMHO, compose.yaml is the best balance of convenience and simplicity if you need one (or even "several") instances. You should only get more fancy if you need to deploy `n` instances with auto provision/load-balancing/failover/etc.
1 comments

It seems to me that converting docker-compose to kubernetes is fairly straightforward too.
Hey, thank you for the feedback. I have created an issue to add a quick start for Kubernetes as well. Most of my decisions behind this project is to make it super "dumb" and easy to use. Thank you so much for the feedback!
Ah, I was thinking more from the perspective of the consuming party ;)

Though of course it’s nice if you pre-add it, it’s nothing people can’t do themselves.