Docker Compose best practices for dev and prod
If you don't use the same Docker Compose file for Production, don't use it for Development. Your two different systems will diverge in behavior, leading you to troubleshoot two separate sets of problems, and testing being unreliable, defeating the whole "it just runs everywhere" premise.<p>Docker Compose is fine for running smoke tests/unit tests, but if Dev and Prod run differently, there's really no point to using Docker Compose other than developing without internet access.<p>(It goes without saying that Docker Compose only works on <i>a single host</i>, so that won't work for Prod if you need more than one host, but single-host-everything seems to be HN's current fetish)