From 0b68808472194346996ad42c857e817da0f08d39 Mon Sep 17 00:00:00 2001 From: Damian Bast Date: Thu, 8 May 2025 09:45:16 +0200 Subject: [PATCH] fix: Switch to new compose tool --- docs/01-get-started/03-working-with-the-database.md | 2 +- docs/06-concepts/11-authentication/01-setup.md | 2 +- docs/06-concepts/19-testing/01-get-started.md | 2 +- docs/08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- docs/08-upgrading/05-upgrade-to-pgvector.md | 4 ++-- versioned_docs/version-1.0.0/07-contribute.md | 2 +- versioned_docs/version-1.0.0/index.md | 6 +++--- versioned_docs/version-1.1.0/08-contribute.md | 2 +- versioned_docs/version-1.1.0/index.md | 6 +++--- .../05-concepts/09-authentication/01-setup.mdx | 2 +- versioned_docs/version-1.1.1/09-contribute.md | 2 +- .../version-1.2.0/05-concepts/10-authentication/01-setup.md | 2 +- versioned_docs/version-1.2.0/11-contribute.md | 2 +- .../12-upgrading/01-upgrade-to-one-point-two.md | 4 ++-- .../version-2.0.0/05-concepts/10-authentication/01-setup.md | 2 +- versioned_docs/version-2.0.0/11-contribute.md | 2 +- .../12-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../version-2.1.0/06-concepts/11-authentication/01-setup.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- versioned_docs/version-2.1.0/10-contribute.md | 2 +- .../version-2.2.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.2.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- versioned_docs/version-2.2.0/10-contribute.md | 2 +- .../version-2.3.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.3.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../version-2.4.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.4.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../version-2.5.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.5.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../version-2.6.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.6.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../01-get-started/03-working-with-the-database.md | 2 +- .../version-2.7.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.7.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../01-get-started/03-working-with-the-database.md | 2 +- .../version-2.8.0/06-concepts/11-authentication/01-setup.md | 2 +- .../version-2.8.0/06-concepts/19-testing/01-get-started.md | 2 +- .../08-upgrading/02-upgrade-to-one-point-two.md | 4 ++-- .../version-2.8.0/08-upgrading/05-upgrade-to-pgvector.md | 4 ++-- 45 files changed, 62 insertions(+), 62 deletions(-) diff --git a/docs/01-get-started/03-working-with-the-database.md b/docs/01-get-started/03-working-with-the-database.md index 93d653c6..fcaa35c4 100644 --- a/docs/01-get-started/03-working-with-the-database.md +++ b/docs/01-get-started/03-working-with-the-database.md @@ -422,7 +422,7 @@ First, we need to start the server and apply the migrations by adding the `--app ```bash $ cd magic_recipe/magic_recipe_server -$ docker-compose up -d +$ docker compose up -d $ dart bin/main.dart --apply-migrations ``` diff --git a/docs/06-concepts/11-authentication/01-setup.md b/docs/06-concepts/11-authentication/01-setup.md index ffbd3aa1..4a04e210 100644 --- a/docs/06-concepts/11-authentication/01-setup.md +++ b/docs/06-concepts/11-authentication/01-setup.md @@ -60,7 +60,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/docs/06-concepts/19-testing/01-get-started.md b/docs/06-concepts/19-testing/01-get-started.md index a80ba8e5..a05d7cbe 100644 --- a/docs/06-concepts/19-testing/01-get-started.md +++ b/docs/06-concepts/19-testing/01-get-started.md @@ -213,7 +213,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/docs/08-upgrading/02-upgrade-to-one-point-two.md b/docs/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/docs/08-upgrading/02-upgrade-to-one-point-two.md +++ b/docs/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/docs/08-upgrading/05-upgrade-to-pgvector.md b/docs/08-upgrading/05-upgrade-to-pgvector.md index aeaab00f..24896009 100644 --- a/docs/08-upgrading/05-upgrade-to-pgvector.md +++ b/docs/08-upgrading/05-upgrade-to-pgvector.md @@ -45,8 +45,8 @@ services: 2. Recreate your containers to use the new image: ```bash -docker-compose down -docker-compose up -d +docker compose down +docker compose up -d ``` diff --git a/versioned_docs/version-1.0.0/07-contribute.md b/versioned_docs/version-1.0.0/07-contribute.md index d7bdb17c..de733572 100644 --- a/versioned_docs/version-1.0.0/07-contribute.md +++ b/versioned_docs/version-1.0.0/07-contribute.md @@ -34,7 +34,7 @@ Running single individual tests is useful when you are working on a specific fea 2. Start the Docker container for the test server. ```bash cd tests/serverpod_test_server/docker_local -docker-compose up --build --detach +docker compose up --build --detach ./setup-tables ``` 3. Start the test server. diff --git a/versioned_docs/version-1.0.0/index.md b/versioned_docs/version-1.0.0/index.md index 478efc9e..6a42f3b4 100644 --- a/versioned_docs/version-1.0.0/index.md +++ b/versioned_docs/version-1.0.0/index.md @@ -58,11 +58,11 @@ It can take up to a few minutes the first time you run `serverpod create`. This ::: ## Starting the server -Start your Docker containers with `docker-compose up --build --detach`. It will start Postgres and Redis. Then, run `dart bin/main.dart` to start your server. +Start your Docker containers with `docker compose up --build --detach`. It will start Postgres and Redis. Then, run `dart bin/main.dart` to start your server. ```bash cd mypod/mypod_server -docker-compose up --build --detach +docker compose up --build --detach dart bin/main.dart ``` @@ -77,6 +77,6 @@ Webserver listening on port 8082 :::info -If you need to stop the Docker containers at some point, just run `docker-compose stop` or use the Docker Desktop application. You can also use Docker Desktop to start, stop, and manage your containers. +If you need to stop the Docker containers at some point, just run `docker compose stop` or use the Docker Desktop application. You can also use Docker Desktop to start, stop, and manage your containers. ::: diff --git a/versioned_docs/version-1.1.0/08-contribute.md b/versioned_docs/version-1.1.0/08-contribute.md index 3e6c9d2c..bed4a928 100644 --- a/versioned_docs/version-1.1.0/08-contribute.md +++ b/versioned_docs/version-1.1.0/08-contribute.md @@ -47,7 +47,7 @@ Running single individual tests is useful when you are working on a specific fea 2. Start the Docker container for the test server. ```bash cd tests/serverpod_test_server/docker_local -docker-compose up --build --detach +docker compose up --build --detach ./setup-tables ``` 3. Start the test server. diff --git a/versioned_docs/version-1.1.0/index.md b/versioned_docs/version-1.1.0/index.md index 1a026de4..f7d230c5 100644 --- a/versioned_docs/version-1.1.0/index.md +++ b/versioned_docs/version-1.1.0/index.md @@ -58,11 +58,11 @@ It can take up to a few minutes the first time you run `serverpod create`. This ::: ## Starting the server -Start your Docker containers with `docker-compose up --build --detach`. It will start Postgres and Redis. Then, run `dart bin/main.dart` to start your server. +Start your Docker containers with `docker compose up --build --detach`. It will start Postgres and Redis. Then, run `dart bin/main.dart` to start your server. ```bash cd mypod/mypod_server -docker-compose up --build --detach +docker compose up --build --detach dart bin/main.dart ``` @@ -77,6 +77,6 @@ Webserver listening on port 8082 :::info -If you need to stop the Docker containers at some point, just run `docker-compose stop` or use the Docker Desktop application. You can also use Docker Desktop to start, stop, and manage your containers. +If you need to stop the Docker containers at some point, just run `docker compose stop` or use the Docker Desktop application. You can also use Docker Desktop to start, stop, and manage your containers. ::: diff --git a/versioned_docs/version-1.1.1/05-concepts/09-authentication/01-setup.mdx b/versioned_docs/version-1.1.1/05-concepts/09-authentication/01-setup.mdx index 900300df..af3787ea 100644 --- a/versioned_docs/version-1.1.1/05-concepts/09-authentication/01-setup.mdx +++ b/versioned_docs/version-1.1.1/05-concepts/09-authentication/01-setup.mdx @@ -42,7 +42,7 @@ $ serverpod generate Start your database container from the server project. ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` [Copy / Download](https://github.com/serverpod/serverpod/blob/main/modules/serverpod_auth/serverpod_auth_server/generated/tables.pgsql) the table definitions for the auth module. Save them as `tables-auth.pgsql` in the `generated` folder of your server project. diff --git a/versioned_docs/version-1.1.1/09-contribute.md b/versioned_docs/version-1.1.1/09-contribute.md index 896d613a..9b677e2a 100644 --- a/versioned_docs/version-1.1.1/09-contribute.md +++ b/versioned_docs/version-1.1.1/09-contribute.md @@ -40,7 +40,7 @@ Running single individual tests is useful when you are working on a specific fea 2. Start the Docker container for the test server. ```bash cd tests/serverpod_test_server/docker_local -docker-compose up --build --detach +docker compose up --build --detach ./setup-tables ``` 3. Start the test server. diff --git a/versioned_docs/version-1.2.0/05-concepts/10-authentication/01-setup.md b/versioned_docs/version-1.2.0/05-concepts/10-authentication/01-setup.md index ccbd77b1..3a32b2ec 100644 --- a/versioned_docs/version-1.2.0/05-concepts/10-authentication/01-setup.md +++ b/versioned_docs/version-1.2.0/05-concepts/10-authentication/01-setup.md @@ -45,7 +45,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-1.2.0/11-contribute.md b/versioned_docs/version-1.2.0/11-contribute.md index 2a8bf1ee..f66583eb 100644 --- a/versioned_docs/version-1.2.0/11-contribute.md +++ b/versioned_docs/version-1.2.0/11-contribute.md @@ -40,7 +40,7 @@ Running single individual tests is useful when you are working on a specific fea 2. Start the Docker container for the test server. ```bash $ cd tests/serverpod_test_server/docker-local -$ docker-compose up --build --detach +$ docker compose up --build --detach $ ./setup-tables ``` 3. Start the test server. diff --git a/versioned_docs/version-1.2.0/12-upgrading/01-upgrade-to-one-point-two.md b/versioned_docs/version-1.2.0/12-upgrading/01-upgrade-to-one-point-two.md index 9e6e1781..c58b843a 100644 --- a/versioned_docs/version-1.2.0/12-upgrading/01-upgrade-to-one-point-two.md +++ b/versioned_docs/version-1.2.0/12-upgrading/01-upgrade-to-one-point-two.md @@ -195,8 +195,8 @@ $ serverpod create-migration In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash -$ docker-compose down -v -$ docker-compose up --build --detach +$ docker compose down -v +$ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.0.0/05-concepts/10-authentication/01-setup.md b/versioned_docs/version-2.0.0/05-concepts/10-authentication/01-setup.md index be1b4d89..8101e1c3 100644 --- a/versioned_docs/version-2.0.0/05-concepts/10-authentication/01-setup.md +++ b/versioned_docs/version-2.0.0/05-concepts/10-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.0.0/11-contribute.md b/versioned_docs/version-2.0.0/11-contribute.md index 6caad6cb..7b55cf51 100644 --- a/versioned_docs/version-2.0.0/11-contribute.md +++ b/versioned_docs/version-2.0.0/11-contribute.md @@ -48,7 +48,7 @@ Running single individual tests is useful when you are working on a specific fea ```bash $ cd tests/serverpod_test_server/docker-local - $ docker-compose up --build --detach + $ docker compose up --build --detach $ ./setup-tables ``` diff --git a/versioned_docs/version-2.0.0/12-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.0.0/12-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.0.0/12-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.0.0/12-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.1.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.1.0/06-concepts/11-authentication/01-setup.md index 1550b839..89b49af3 100644 --- a/versioned_docs/version-2.1.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.1.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.1.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.1.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.1.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.1.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.1.0/10-contribute.md b/versioned_docs/version-2.1.0/10-contribute.md index f104d911..262f3d10 100644 --- a/versioned_docs/version-2.1.0/10-contribute.md +++ b/versioned_docs/version-2.1.0/10-contribute.md @@ -51,7 +51,7 @@ Running single individual tests is useful when you are working on a specific fea ```bash $ cd tests/serverpod_test_server/docker-local - $ docker-compose up --build --detach + $ docker compose up --build --detach $ ./setup-tables ``` diff --git a/versioned_docs/version-2.2.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.2.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.2.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.2.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.2.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.2.0/06-concepts/19-testing/01-get-started.md index 78a0b58c..da4fdefb 100644 --- a/versioned_docs/version-2.2.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.2.0/06-concepts/19-testing/01-get-started.md @@ -229,7 +229,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` By default this starts up both the `development` and `test` profiles. To only start one profile, simply add `--profile test` to the command. diff --git a/versioned_docs/version-2.2.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.2.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.2.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.2.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.2.0/10-contribute.md b/versioned_docs/version-2.2.0/10-contribute.md index f104d911..262f3d10 100644 --- a/versioned_docs/version-2.2.0/10-contribute.md +++ b/versioned_docs/version-2.2.0/10-contribute.md @@ -51,7 +51,7 @@ Running single individual tests is useful when you are working on a specific fea ```bash $ cd tests/serverpod_test_server/docker-local - $ docker-compose up --build --detach + $ docker compose up --build --detach $ ./setup-tables ``` diff --git a/versioned_docs/version-2.3.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.3.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.3.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.3.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.3.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.3.0/06-concepts/19-testing/01-get-started.md index 78a0b58c..da4fdefb 100644 --- a/versioned_docs/version-2.3.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.3.0/06-concepts/19-testing/01-get-started.md @@ -229,7 +229,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` By default this starts up both the `development` and `test` profiles. To only start one profile, simply add `--profile test` to the command. diff --git a/versioned_docs/version-2.3.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.3.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.3.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.3.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.4.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.4.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.4.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.4.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.4.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.4.0/06-concepts/19-testing/01-get-started.md index dc71714a..347c496e 100644 --- a/versioned_docs/version-2.4.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.4.0/06-concepts/19-testing/01-get-started.md @@ -211,7 +211,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/versioned_docs/version-2.4.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.4.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.4.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.4.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.5.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.5.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.5.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.5.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.5.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.5.0/06-concepts/19-testing/01-get-started.md index dc71714a..347c496e 100644 --- a/versioned_docs/version-2.5.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.5.0/06-concepts/19-testing/01-get-started.md @@ -211,7 +211,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/versioned_docs/version-2.5.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.5.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.5.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.5.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.6.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.6.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.6.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.6.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.6.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.6.0/06-concepts/19-testing/01-get-started.md index dc71714a..347c496e 100644 --- a/versioned_docs/version-2.6.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.6.0/06-concepts/19-testing/01-get-started.md @@ -211,7 +211,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/versioned_docs/version-2.6.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.6.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.6.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.6.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.7.0/01-get-started/03-working-with-the-database.md b/versioned_docs/version-2.7.0/01-get-started/03-working-with-the-database.md index 93d653c6..fcaa35c4 100644 --- a/versioned_docs/version-2.7.0/01-get-started/03-working-with-the-database.md +++ b/versioned_docs/version-2.7.0/01-get-started/03-working-with-the-database.md @@ -422,7 +422,7 @@ First, we need to start the server and apply the migrations by adding the `--app ```bash $ cd magic_recipe/magic_recipe_server -$ docker-compose up -d +$ docker compose up -d $ dart bin/main.dart --apply-migrations ``` diff --git a/versioned_docs/version-2.7.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.7.0/06-concepts/11-authentication/01-setup.md index 86406f8c..66c10d7d 100644 --- a/versioned_docs/version-2.7.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.7.0/06-concepts/11-authentication/01-setup.md @@ -59,7 +59,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.7.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.7.0/06-concepts/19-testing/01-get-started.md index dc71714a..347c496e 100644 --- a/versioned_docs/version-2.7.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.7.0/06-concepts/19-testing/01-get-started.md @@ -211,7 +211,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/versioned_docs/version-2.7.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.7.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.7.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.7.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.8.0/01-get-started/03-working-with-the-database.md b/versioned_docs/version-2.8.0/01-get-started/03-working-with-the-database.md index 93d653c6..fcaa35c4 100644 --- a/versioned_docs/version-2.8.0/01-get-started/03-working-with-the-database.md +++ b/versioned_docs/version-2.8.0/01-get-started/03-working-with-the-database.md @@ -422,7 +422,7 @@ First, we need to start the server and apply the migrations by adding the `--app ```bash $ cd magic_recipe/magic_recipe_server -$ docker-compose up -d +$ docker compose up -d $ dart bin/main.dart --apply-migrations ``` diff --git a/versioned_docs/version-2.8.0/06-concepts/11-authentication/01-setup.md b/versioned_docs/version-2.8.0/06-concepts/11-authentication/01-setup.md index ffbd3aa1..4a04e210 100644 --- a/versioned_docs/version-2.8.0/06-concepts/11-authentication/01-setup.md +++ b/versioned_docs/version-2.8.0/06-concepts/11-authentication/01-setup.md @@ -60,7 +60,7 @@ $ serverpod create-migration Start your database container from the server project. ```bash -$ docker-compose up --build --detach +$ docker compose up --build --detach ``` Then apply the migration by starting the server with the `apply-migrations` flag. diff --git a/versioned_docs/version-2.8.0/06-concepts/19-testing/01-get-started.md b/versioned_docs/version-2.8.0/06-concepts/19-testing/01-get-started.md index a80ba8e5..a05d7cbe 100644 --- a/versioned_docs/version-2.8.0/06-concepts/19-testing/01-get-started.md +++ b/versioned_docs/version-2.8.0/06-concepts/19-testing/01-get-started.md @@ -213,7 +213,7 @@ The location of the test tools can be changed by changing the `server_test_tool Before the test can be run the Postgres and Redis also have to be started: ```bash -docker-compose up --build --detach +docker compose up --build --detach ``` Now the test is ready to be run: diff --git a/versioned_docs/version-2.8.0/08-upgrading/02-upgrade-to-one-point-two.md b/versioned_docs/version-2.8.0/08-upgrading/02-upgrade-to-one-point-two.md index 501a3581..64db1e6b 100644 --- a/versioned_docs/version-2.8.0/08-upgrading/02-upgrade-to-one-point-two.md +++ b/versioned_docs/version-2.8.0/08-upgrading/02-upgrade-to-one-point-two.md @@ -203,8 +203,8 @@ If it is not important to preserve the data that is in your database, you can si In a Serverpod development project, the database is hosted in a docker container. To remove the existing database and start a new one run the following commands: ```bash - $ docker-compose down -v - $ docker-compose up --build --detach + $ docker compose down -v + $ docker compose up --build --detach ``` The command first removes the running container along with its volume and the second command starts a new database from scratch. diff --git a/versioned_docs/version-2.8.0/08-upgrading/05-upgrade-to-pgvector.md b/versioned_docs/version-2.8.0/08-upgrading/05-upgrade-to-pgvector.md index aeaab00f..24896009 100644 --- a/versioned_docs/version-2.8.0/08-upgrading/05-upgrade-to-pgvector.md +++ b/versioned_docs/version-2.8.0/08-upgrading/05-upgrade-to-pgvector.md @@ -45,8 +45,8 @@ services: 2. Recreate your containers to use the new image: ```bash -docker-compose down -docker-compose up -d +docker compose down +docker compose up -d ```