🐬Sync with codebase: docker compose

Author: dumindu

content/en/docs/a1.hello-world-server.md

@@ -181,14 +181,13 @@ EXPOSE 8080
 > We can use `docker ps` command to see more info. To stop the container `docker stop <name>` and to remove the image `docker rmi -f <image-id>`.
 
 
-## `docker-compose.yml`
+## `compose.yml`
 
-> [📖 Docker Compose](https://docs.docker.com/compose/) is a **tool for defining and running multi-container Docker applications**. With a single command, we can create and start all the services according to the content in the `docker-compose.yml` file. 🔍 If you are new to Docker Compose, I recommend you to read its [**Get Started guild**](https://docs.docker.com/compose/gettingstarted/) on its official documentation.
+> [📖 Docker Compose](https://docs.docker.com/compose/) is a **tool for defining and running multi-container Docker applications**. With a single command, we can create and start all the services according to the content in the `compose.yml` file. 🔍 If you are new to Docker Compose, I recommend you to read its [**Get Started guild**](https://docs.docker.com/compose/gettingstarted/) on its official documentation.
 
-Let’s add the `docker-compose.yml`.
+Let’s add the `compose.yml`.
 
 ```dockerfile
-version: '3'
 services:
 
   app:
@@ -197,9 +196,9 @@ services:
       - "8080:8080"
 ```
 
-- You can use `docker-compose build` and `docker-compose up` commands, to build and run the application.
+- You can use `docker compose build` and `docker compose up` commands, to build and run the application.
 - You should see the same response, `Hello, world!` text while visit [localhost:8080/hello](http://localhost:8080/hello) in the browser.
-- Use the `docker-compose down` command to stop the application.
+- Use the `docker compose down` command to stop the application.
 
 
 ## An idiomatic structure

content/en/docs/a2.database-and-migrations.md

@@ -4,7 +4,7 @@ slug: "database-and-migrations"
 ---
 
 > **👨‍🏫 Before we start...**
-> - We'll run a Postgres database via `docker-compose`.
+> - We'll run a Postgres database via `docker compose`.
 > - There are a few popular database migration tools in the Go ecosystem, like [`golang-migrate/migrate`](https://github.com/golang-migrate/migrate), [`pressly/goose`](https://github.com/pressly/goose), [GORM migrations](http://gorm.io/docs/migration.html), etc. We selected [`pressly/goose`](https://github.com/pressly/goose) due to its simplicity, lesser resource usage, and customizability. But, instead of using its prebuilt binaries, we'll build a custom binary with static drivers, settings, and more simplified commands.
 > - ⭐ We'll store all `SQL` database migration files in the `migrations` folder in the project root.
 
@@ -30,10 +30,9 @@ In this article series, we are building a RESTful CRUD API for a simple bookshel
 
 We'll use the [official Postgres Alpine Docker image](https://hub.docker.com/_/postgres) to build our development database.
 
-Let's update the `docker-compose.yml` file,
+Let's update the `compose.yml` file,
 
 ```dockerfile
-version: '3'
 services:
 
   app:
@@ -54,9 +53,9 @@ services:
     restart: always
 ```
 
-Run `docker-compose down` and `docker-compose up` to rerun the application with the database. Or, you can run `docker-compose up db` to run only the database.
+Run `docker compose down` and `docker compose up` to rerun the application with the database. Or, you can run `docker compose up db` to run only the database.
 
-We can use `docker-compose ps` commands to see more info about the running containers.
+We can use `docker compose ps` commands to see more info about the running containers.
 
 ```
 NAME                COMMAND                  SERVICE             STATUS              PORTS

content/en/docs/a3.configurations.md

@@ -4,13 +4,13 @@ slug: "configurations"
 ---
 
 > **👨‍🏫 Before we start...**
-> - Configurations can be stored in a variety of formats, such as `.xml`, `.json`, `.env`, `.yaml`, and `.toml` files, as well as systems like [`etcd`](https://etcd.io/), [AWS Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html), and [GCP Runtime Configurator](https://cloud.google.com/deployment-manager/runtime-configurator/). In this project, we will save the configurations in an `.env` file and use `docker-compose` to load them into the development environment.
+> - Configurations can be stored in a variety of formats, such as `.xml`, `.json`, `.env`, `.yaml`, and `.toml` files, as well as systems like [`etcd`](https://etcd.io/), [AWS Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html), and [GCP Runtime Configurator](https://cloud.google.com/deployment-manager/runtime-configurator/). In this project, we will save the configurations in an `.env` file and use `docker compose` to load them into the development environment.
 > - Go standard library provides the [`os.Getenv()`](https://golang.org/pkg/os/#Getenv) function to read each environment variable separately. But there are Go libraries such as [`spf13/viper`](https://github.com/spf13/viper), [`kelseyhightower/envconfig`](https://github.com/kelseyhightower/envconfig), [`caarlos0/env`](https://github.com/caarlos0/env), and [`joeshaw/envdecode`](https://github.com/joeshaw/envdecode) to read environment variables in bulk and populate them as a struct. We choose [`joeshaw/envdecode`](https://github.com/joeshaw/envdecode) for this project because it includes validations, zero-dependency, and ease of use.
 
 
 ## Populate environment variables with Docker
 
-💡 We use `docker-compose` with the [`env_file`](https://docs.docker.com/compose/compose-file/compose-file-v3/#env_file) option to load the environment variables into the development environment. If you are using `docker run`, you can use the [`--env-file` option](https://docs.docker.com/engine/reference/commandline/run/#options) with it.
+💡 We use `docker compose` with the [`env_file`](https://docs.docker.com/compose/compose-file/compose-file-v3/#env_file) option to load the environment variables into the development environment. If you are using `docker run`, you can use the [`--env-file` option](https://docs.docker.com/engine/reference/commandline/run/#options) with it.
 
 ### 1. Add `.env`
 
@@ -31,7 +31,7 @@ DB_DEBUG=true
 
 > 💡 `SERVER_DEBUG` and `DB_DEBUG` will be utilized with the application logs and the GORM logs in the future steps. 
 
-### 2. update `docker-compose.yml`
+### 2. update `compose.yml`
 
 ```yml
   app:
@@ -43,7 +43,7 @@ DB_DEBUG=true
       - db
 ```
 
-Run `docker-compose down` and `docker-compose up` to populate the environment variables into the development environment.
+Run `docker compose down` and `docker compose up` to populate the environment variables into the development environment.
 
 
 ## Adding configs to the API
@@ -201,7 +201,7 @@ func main() {
 }
 ```
 
-Run `docker-compose down`, `docker-compose build` and `docker-compose up` to run the application with the recent changes.
+Run `docker compose down`, `docker compose build` and `docker compose up` to run the application with the recent changes.
 
 ### 5. Run `go mod tidy`
 
@@ -212,10 +212,9 @@ When we add a new package and use it, we have to run `go mod tidy` to reorganize
 
 > 💡 Because we hardcoded `localhost` for the database host in the previous article, we encountered the `migrate up: dial tcp 127.0.0.1:3306: connect: connection refused` error with the `./bin/migrate up` command. But, with the current configurations, we should be able to run `./bin/migrate up` inside the docker image with the correct host. So, let's automate running migrations on application startup.
 
-Usually, starting the database takes more time. So, we need to wait until the database is up before running database migrations. For this, we use `docker-compose` `db:`[`healthcheck`](https://docs.docker.com/compose/compose-file/#healthcheck) and `app:`[`depends_on:db:condition`](https://docs.docker.com/compose/compose-file/#depends_on) options.
+Usually, starting the database takes more time. So, we need to wait until the database is up before running database migrations. For this, we use `docker compose` `db:`[`healthcheck`](https://docs.docker.com/compose/compose-file/#healthcheck) and `app:`[`depends_on:db:condition`](https://docs.docker.com/compose/compose-file/#depends_on) options.
 
 ```yml
-version: '3.9'
 services:
 
   app:

content/en/docs/a4.routes-and-openapi-specification.md

@@ -149,7 +149,7 @@ func main() {
 When we add a new package and use it, we have to run `go mod tidy` to reorganize the dependencies in the `go.mod` file.
 
 
-> 💡 You can use the `docker-compose down`, `docker-compose build`, and `docker-compose up` commands, to build and run the API application to test the recent changes. Alternatively, you can configure your IDE to run `cmd/api/main.go` locally, with the required env variables; Ex: [Running applications in the GoLand IDE](https://www.jetbrains.com/help/go/running-applications.html)
+> 💡 You can use the `docker compose down`, `docker compose build`, and `docker compose up` commands, to build and run the API application to test the recent changes. Alternatively, you can configure your IDE to run `cmd/api/main.go` locally, with the required env variables; Ex: [Running applications in the GoLand IDE](https://www.jetbrains.com/help/go/running-applications.html)
 
 
 ## Generating OpenAPI specification