[fideloper]

It's good info as far as Dockerizing the build process of a React app, but there isn't much deploying happening in this article. docker-compose isn't really used for deployment (unless you're one of the 3 people using Swarm).

I think the deployment story for for React apps is monopolized by all the at-the-edge startups, and they don't run containers(?). Even Fly.io doesn't run containers (you make a Docker image as your "deployment artifact", and Fly creates a Firecracker-friendly VM from it).

[marginalia_nu]

I think docker-compose seems very appropriate for this use case. It's not like this container is going to benefit from running in a cluster.

[ljm]

I mean, I wouldn't deploy static content inside a docker container running nginx when you can just use a tiny busybox image for it. Let nginx sit on top of it all so you only have one instance of it running, instead of one in every image

[golergka]

Honest question — may be I don't know something. Is there something wrong with using Docker compose in production to deploy a simple system of ~5 services?

[morbicer]

It's fine if you don't care about things like: redundancy/HA, zero-downtime, liveness probes, auto-scaling. So fine for smaller projects. But if you have small project it begs a question why do you have 5 services.

[VoodooJuJu]

docker-compose absolutely gets deployment done, my bank account can corroborate this.

[WendyTheWillow]

I’ve run a SaaS platform with dozens of customers using docker-compose on an ec2 in production for over a year.

[pinkgolem]

We are using docker compose on 2 vms behind a loadbalancer, works like a charm & is pretty quick