> Docker-compose isn't going to help you with Let's Encrypt, you're going to need to keep resolving that problem with each app you have A very common pattern i

> Docker-compose isn't going to help you with Let's Encrypt, you're going to need to keep resolving that problem with each app you have A very common pattern is to front containerised HTTP services with a proxy, most typically nginx, Haproxy or Traefik, and have them do TLS termination - so you only have to deal with setting up Let's Encrypt for the proxy. For Traefik, that's really simple to setup (in general I actually find Traefik quite fiddly to configure, but for Let's Encrypt it's simple). For nginx, there are numerous sidecar images available that handle it for you, such as nginx-proxy. I haven't used Haproxy, but I would imagine it's the same ease of setup. > You will not use docker-compose at your job I do, and I've seen it used quite on development projects, so that developers can reliably and consistently run services locally.