docker compose
don’t really like it when people include nginx or other reverse proxy directly in the compose for that “complete hands free setup”
almost everybody will run a proxy outside of it anyway

@eru So true. I guess they just pretend that everyone runs VMs for every single service or something?

@stefan yeah maybe
i find its often done when multiple services are run in the container and you need some routing, makes development easier to just stuff it inside a compose.yml (for those that like developing using docker for some reason i can never fathom)
and people might claim its easier, just pull the container and it works, not need to do separate reverse proxy config

@stefan the proper solution would be to either add something to your app to handle complicated routing, or document what traffic needs to go where and have an example nginx.conf or something
if you insist on developing in docker, you should have separate dev and production compose.yml’s anyway

@eru I mostly end up kicking nginx out of the compose file and use my normal (bare metal) nginx but finding thr right confing for nginx to work is a pain sometimes still.

Maybe I just hate docker in general too much