s/docker-compose/docker compose/ in README

Author: oalders

README.md

@@ -2,7 +2,7 @@
 
 [![CircleCI](https://circleci.com/gh/metacpan/metacpan-docker.svg?style=svg)](https://circleci.com/gh/metacpan/metacpan-docker)
 
-![docker-compose up](https://github.com/metacpan/metacpan-docker/workflows/docker-compose%20up/badge.svg?branch=master)
+![docker compose up](https://github.com/metacpan/metacpan-docker/workflows/docker-compose%20up/badge.svg?branch=master)
 
 <!-- vim-markdown-toc GFM -->
 
@@ -80,8 +80,8 @@ command:
 
     docker pull elasticsearch:2.4 --platform=linux/x86_64
 
-It is highly recommended that you alias `docker-compose` to `fig` (its original
-name) and use it wherever `docker-compose` is used. You are going to have to
+It is highly recommended that you alias `docker compose` to `fig` (its original
+name) and use it wherever `docker compose` is used. You are going to have to
 type this command a lot.
 
 Then, clone this repo and set up the environment:
@@ -101,10 +101,10 @@ These repositories are automatically mounted into the appropriate docker
 containers allowing the developer to use their preferred tools to work with the
 source code.
 
-The `docker-compose up` command on its own will bring up the entire stack in the
+The `docker compose up` command on its own will bring up the entire stack in the
 foreground (logs will be displayed).
 
-The `docker-compose up` command will also fetch the official container images
+The `docker compose up` command will also fetch the official container images
 from [MetaCPAN Docker Hub](https://cloud.docker.com/u/metacpan/repository/list)
 repositories.
 
@@ -115,7 +115,7 @@ Docker) and run the services.
 Don't forget to seed the local `metacpan-api` with a partial CPAN; run the
 following command in a separate terminal to get yourself up to speed:
 
-    docker-compose exec api index-cpan.sh
+    docker compose exec api index-cpan.sh
 
 This will prompt you to confirm removing old indices and setting up mappings on
 the Elasticsearch service (say `YES`). It will then proceed to rsync a partial
@@ -128,7 +128,7 @@ elsewhere.
 Alternatively, if you just want to hack on the web frontend, you can run this
 instead of all the above:
 
-    docker-compose up web
+    docker compose up web
 
 From here, you can proceed and hack on the MetaCPAN code at `src/metacpan-api`
 and/or `src/metacpan-web` directories, and saving edits will reload the
@@ -137,7 +137,7 @@ corresponding apps automatically!
 When done hacking (or, more likely, when you need to rebuild/refresh your Docker
 environment) you can then run
 
-    docker-compose down
+    docker compose down
 
 in another terminal to stop all MetaCPAN services and remove the containers.
 
@@ -150,26 +150,26 @@ For further details, read on!
 You can (re)build arbitrary containers. For instance, if you want to rebuild the
 `api` container:
 
-    docker-compose build api
+    docker compose build api
 
 ### Accessing Containers
 
-Containers are accessible via the `docker-compose exec` command followed by the
+Containers are accessible via the `docker compose exec` command followed by the
 container and then the command to execute. For example, to start a shell prompt
 in the `api` container:
 
-    docker-compose exec api /bin/bash
+    docker compose exec api /bin/bash
 
 Executing tests via `prove` inside the API container:
 
-    docker-compose exec api_test prove -lvr \
+    docker compose exec api_test prove -lvr \
       t/00_setup.t \
       t/01_darkpan.t \
       t/api/controller/cover.t
 
 To access the `psql` command line client in the PostgreSQL container:
 
-    docker-compose exec pgdb psql
+    docker compose exec pgdb psql
 
 ### Accessing Services
 
@@ -217,11 +217,11 @@ directly. They are available via the `api` and `api_test` containers.
 
 You can query the `elasticsearch` container via:
 
-    docker-compose exec elasticsearch curl http://localhost:9200
+    docker compose exec elasticsearch curl http://localhost:9200
 
 You can query the `elasticsearch_test` container via:
 
-    docker-compose exec elasticsearch_test curl http://localhost:9200
+    docker compose exec elasticsearch_test curl http://localhost:9200
 
 #### `PostgreSQL`
 
@@ -267,21 +267,21 @@ These services use one or more Docker volumes:
 [4]: https://metacpan.org/pod/Carton
 
 Docker Compose is used to, uh, _compose_ them all together into one system.
-Using `docker-compose` directly is a mouthful, however, so putting this all
+Using `docker compose` directly is a mouthful, however, so putting this all
 together is done via the `bin/metacpan-docker` script to simplify setup and
 usage (and to get you started hacking on the MetaCPAN sooner!)
 
 ### The `bin/metacpan-docker` script
 
-`bin/metacpan-docker` is a thin wrapper around the `docker-compose` command,
+`bin/metacpan-docker` is a thin wrapper around the `docker compose` command,
 providing the environment variables necessary to run a basic MetaCPAN
 environment. It provides these subcommands:
 
 #### `bin/metacpan init`
 
 The `init` subcommand basically clones the [metacpan-api][5] and
 [metacpan-web][6] repositories, and sets up the git commit hooks for each of
-them, in preparation for future `docker-compose` or
+them, in preparation for future `docker compose` or
 `bin/metacpan-docker localapi` commands.
 
 It also clones the `metacpan-grep-front-end` and `metacpan-cpan-extracted-lite`
@@ -292,12 +292,12 @@ repositories.
 
 #### `bin/metacpan localapi`
 
-The `localapi` subcommand adds the necessary configuration for `docker-compose`
+The `localapi` subcommand adds the necessary configuration for `docker compose`
 to run both the `metacpan-web` and `metacpan-api` services, along with
 `elasticsearch` and Docker volumes. Under the hood, it customizes the
 `COMPOSE_FILE` and `COMPOSE_PROJECT_NAME` environment variables used by
-`docker-compose` to use additional YAML configuration files aside from the
-default `docker-compose.yml`.
+`docker compose` to use additional YAML configuration files aside from the
+default `docker compose.yml`.
 
 #### `bin/metacpan-docker pull`
 
@@ -314,8 +314,8 @@ command.
 #### `bin/metacpan-docker` build/up/down/start/stop/run/ps/top...
 
 As noted earlier, `bin/metacpan-docker` is a thin wrapper around
-`docker-compose`, so commands like `up`, `down`, and `run` will work as expected
-from `docker-compose`. See the [docker-compose docs][7] for an overview of
+`docker compose`, so commands like `up`, `down`, and `run` will work as expected
+from `docker compose`. See the [docker compose docs][7] for an overview of
 available commands.
 
 [7]:
@@ -329,8 +329,8 @@ The `web` service is a checkout of `metacpan-web`, built as a Docker image.
 Running this service alone is enough if you want to just hack on the frontend,
 since by default the service is configured to talk to
 [https://fastapi.metacpan.org](https://fastapi.metacpan.org) for its backend; if
-this is what you want, then you can simply invoke `docker-compose up` or
-`docker-compose up web`.
+this is what you want, then you can simply invoke `docker compose up` or
+`docker compose up web`.
 
 #### `api`
 
@@ -396,7 +396,7 @@ the [metacpan-puppet][10] repository. The `api` service depends on the
 ### Running your own miniCPAN inside metacpan-docker
 
 Suppose you have a local minicpan in `/home/ftp/pub/CPAN`. If you would like to
-use this in `metacpan-docker`, then edit the `docker-compose.localapi.yml` to
+use this in `metacpan-docker`, then edit the `docker compose.localapi.yml` to
 change the `api` service's volume mounts to use your local minicpan as `/CPAN`,
 e.g.:
 
@@ -450,7 +450,7 @@ You can use `bin/metacpan-docker pull` to update all `src/*` directories.
 
 ### Running Kibana to peek into Elasticsearch data
 
-By default, the `docker-compose.localapi.yml` configures the `elasticsearch`
+By default, the `docker compose.localapi.yml` configures the `elasticsearch`
 service to listen on the Docker host at
 [http://localhost:9200](http://localhost:9200), and is also accessible via the
 Docker `default` network address of