Thanks for agreeing.
Maybe it helps to understand that Docker Compose is really no magic. It’s “just a Python script” that wires Docker containers together, based on a YAML description. It’s what you would do with Docker on the command line manually, wiring up containers, volumes and networking services. Technically, what is running underneath is plain Docker.
With tools like Kompose you can create a Kubernetes (aka OpenShift) configuration that makes the same or a very similar configuration run on a Kubernetes stack. Even simpler, you could run a Docker Compose configuration with Docker Swarm (though I must admit, I haven’t tried this yet).
While “in production” and “for development” are technically two different places, I believe it’s imperative to keep the two environments as similar as possible. There are still developers (and admins) that apply changes to systems running in production. This is dangerous and not the way we should do software in 2018.
That’s what the whole buzz of Foreman-Docker-Compose is about (or at least, what it means to me). We need to bring the two worlds together. It’s a DevOps world, we’re moving our Ops knowledge into the development process, and this has only advantages.