From 3ad69345c3157da4494d81956a4da2ccf11e226a Mon Sep 17 00:00:00 2001 From: Michael Irwin Date: Wed, 23 Nov 2022 11:42:16 -0500 Subject: [PATCH] Update two other instances of "docker-compose" to "docker compose" Signed-off-by: Michael Irwin --- README.md | 2 +- docs/tutorial/what-next/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 41d8365..786ea5a 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ This project has a `docker-compose.yml` file, which will start the mkdocs applic local machine and help you see changes instantly. ```bash -docker-compose up +docker compose up ``` ## Contributing diff --git a/docs/tutorial/what-next/index.md b/docs/tutorial/what-next/index.md index 8eca969..0e305d5 100644 --- a/docs/tutorial/what-next/index.md +++ b/docs/tutorial/what-next/index.md @@ -5,7 +5,7 @@ We're not going to go deep-dive here, but here are a few other areas to look at ## Container Orchestration Running containers in production is tough. You don't want to log into a machine and simply run a -`docker run` or `docker-compose up`. Why not? Well, what happens if the containers die? How do you +`docker run` or `docker compose up`. Why not? Well, what happens if the containers die? How do you scale across several machines? Container orchestration solves this problem. Tools like Kubernetes, Swarm, Nomad, and ECS all help solve this problem, all in slightly different ways.