Use proper command of docker compose and proper name of Docker Compose

Add Docker Compose to glossary

Author: stevepiercy

docs/glossary.md

@@ -289,6 +289,9 @@ DPI
 Docker
     [Docker](https://www.docker.com/) is an open platform for developing, shipping, and running applications using containers.
 
+Docker Compose
+    [Docker Compose](https://docs.docker.com/compose/) is a tool for defining and running multi-container Docker applications.
+
 RelStorage
     [RelStorage](https://relstorage.readthedocs.io/en/latest/) is a storage implementation for ZODB that stores pickles in a relational database.
 

docs/install/containers/examples/haproxy-plone-zeo.md

@@ -63,7 +63,7 @@ volumes:
 
 ## Build the project with multiple backends
 
-Run `docker-compose up -d --scale backend=4` from your project directory.
+Run `docker compose up -d --scale backend=4` from your project directory.
 
 
 ## Access Plone via Browser
@@ -82,6 +82,6 @@ You should see HAProxy statistics for your Plone cluster.
 
 ## Shutdown and cleanup
 
-The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+The command `docker compose down` removes the containers and default network, but preserves the Plone database.
 
-The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.
+The command `docker compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/examples/index.md

@@ -19,7 +19,7 @@ nginx-plone
 haproxy-plone-zeo
 ```
 
-Examples of projects running Plone using `docker-compose`.
+Examples of projects running Plone using `docker compose`.
 
 | Project example | Description |
 | --- | --- |

docs/install/containers/examples/nginx-plone.md

@@ -57,7 +57,7 @@ server {
 You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
 ```
 
-### Service configuration with `docker-compose`
+### Service configuration with Docker Compose
 
 Now let's create a `docker-compose.yml` file:
 
@@ -91,10 +91,10 @@ volumes:
 
 ## Build the project
 
-Start the stack with `docker-compose`.
+Start the stack with `docker compose`.
 
 ```shell
-docker-compose up -d
+docker compose up -d
 ```
 
 This pulls the needed images and starts Plone.
@@ -107,6 +107,6 @@ After startup, go to `http://plone.localhost/` and you should see the site.
 
 ## Shutdown and cleanup
 
-The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+The command `docker compose down` removes the containers and default network, but preserves the Plone database.
 
-The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.
+The command `docker compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/examples/nginx-volto-plone-postgresql.md

@@ -83,7 +83,7 @@ You can either use `localhost`, or add it in your `etc/hosts` file or DNS to poi
 ```
 
 
-### Service configuration with `docker-compose`
+### Service configuration with Docker Compose
 
 Now let's create a `docker-compose.yml` file:
 
@@ -138,10 +138,10 @@ volumes:
 
 ## Build the project
 
-Start the stack with `docker-compose`.
+Start the stack with `docker compose`.
 
 ```shell
-docker-compose up -d
+docker compose up -d
 ```
 
 This pulls the needed images and starts Plone.
@@ -154,15 +154,15 @@ After startup, go to `http://plone.localhost/` and you should see the site.
 
 ## Increase the number of backends
 
-To use two containers for backend, run `docker-compose` with `--scale`.
+To use two containers for backend, run `docker compose` with `--scale`.
 
 ```shell
-docker-compose up --scale backend=2
+docker compose up --scale backend=2
 ```
 
 
 ## Shutdown and cleanup
 
-The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+The command `docker compose down` removes the containers and default network, but preserves the Plone database.
 
-The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.
+The command `docker compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/examples/nginx-volto-plone-zeo.md

@@ -83,7 +83,7 @@ You can either use `localhost`, or add it in your `etc/hosts` file or DNS to poi
 ```
 
 
-### Service configuration with `docker-compose`
+### Service configuration with Docker Compose
 
 Now let's create a `docker-compose.yml` file:
 
@@ -135,10 +135,10 @@ volumes:
 
 ## Build the project
 
-Start the stack with `docker-compose`.
+Start the stack with `docker compose`.
 
 ```shell
-docker-compose up -d
+docker compose up -d
 ```
 
 This pulls the needed images and starts Plone.
@@ -151,15 +151,15 @@ After startup, go to `http://plone.localhost/` and you should see the site.
 
 ## Increase the number of backends
 
-To use two containers for the backend, run `docker-compose` with `--scale`.
+To use two containers for the backend, run `docker compose` with `--scale`.
 
 ```shell
-docker-compose up --scale backend=2
+docker compose up --scale backend=2
 ```
 
 
 ## Shutdown and cleanup
 
-The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+The command `docker compose down` removes the containers and default network, but preserves the Plone database.
 
-The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.
+The command `docker compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/examples/nginx-volto-plone.md

@@ -81,7 +81,7 @@ server {
 You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
 ```
 
-### Service configuration with `docker-compose`
+### Service configuration with Docker Compose
 
 Now let's create a `docker-compose.yml` file:
 
@@ -124,10 +124,10 @@ volumes:
 
 ## Build the project
 
-Start the stack with `docker-compose`.
+Start the stack with `docker compose`.
 
 ```shell
-docker-compose up -d
+docker compose up -d
 ```
 
 This pulls the needed images and starts Plone.
@@ -140,6 +140,6 @@ After startup, go to `http://plone.localhost/` and you should see the site.
 
 ## Shutdown and cleanup
 
-The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+The command `docker compose down` removes the containers and default network, but preserves the Plone database.
 
-The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.
+The command `docker compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/images/frontend.md

@@ -100,7 +100,7 @@ services:
 
 To start, run
 ```shell
-docker-compose up -d
+docker compose up -d
 ```     
 
 ## Versions

docs/install/containers/images/zeo.md

@@ -23,7 +23,7 @@ docker run -p 8100:8100 plone/plone-zeo:latest
 ```
 
 
-### Docker-compose
+### Service configuration with Docker Compose
 
 Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Plone instance and the ZEO instance with volume mounts for data persistence:
 
@@ -51,7 +51,7 @@ volumes:
   data: {}
 ```
 
-Now, run `docker-compose up -d` from your project directory.
+Now, run `docker compose up -d` from your project directory.
 
 Point your browser at http://localhost:8080 and you should see the default Plone site creation page.