eric/docker-getting-started
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update two other instances of "docker-compose" to "docker compose"

Browse Source 
Signed-off-by: Michael Irwin <mikesir87@gmail.com>
This commit is contained in:
Michael Irwin 2022-11-23 11:42:16 -05:00
parent 7e006777d7
commit 3ad69345c3
No known key found for this signature in database
GPG Key ID: 8C42FBB0E482C8CF
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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

2
docs/tutorial/what-next/index.md
View File

@ -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.