chore: 'docker-compose'->'docker compose'

Author: mariuswinger

.github/workflows/tests.yaml

@@ -54,10 +54,10 @@ jobs:
 
       - name: BDD Integration tests
         if: ${{ false }} # disable for now
-        run: docker-compose -f docker-compose.yml -f docker-compose.ci.yml run api behave
+        run: docker compose -f docker-compose.yml -f docker-compose.ci.yml run api behave
 
       - name: Pytest Integration tests
-        run: docker-compose -f docker-compose.yml -f docker-compose.ci.yml run --rm api pytest --integration
+        run: docker compose -f docker-compose.yml -f docker-compose.ci.yml run --rm api pytest --integration
 
   test-web:
     runs-on: ubuntu-latest

documentation/docs/about/running/03-starting-services.md

@@ -3,7 +3,7 @@
 You can start running:
 
 ```shell
-docker-compose up
+docker compose up
 ```
 
 The web app will be served at [http://localhost](http://localhost)

documentation/docs/contribute/01-how-to-start-contributing.md

@@ -33,8 +33,8 @@ git checkout -b feature/my-new-feature
 5. Make the changes in the created branch.
 6. Add and run tests for your changes (we only take pull requests with passing tests).
 ```shell
-docker-compose run --rm api pytest
-docker-compose run --rm web yarn test
+docker compose run --rm api pytest
+docker compose run --rm web yarn test
 ```
 7. Add the changed files
 ```shell

documentation/docs/contribute/development-guide/03-testing.md

@@ -17,7 +17,7 @@ You will find unit tests under `src/tests/unit`.
 <TabItem value="using-docker" label="Using docker">
 
 ```shell
-docker-compose run --rm api pytest
+docker compose run --rm api pytest
 ```
 
 </TabItem>
@@ -50,7 +50,7 @@ These tests depends on mongodb and that it's running.
 <TabItem value="using-docker" label="Using docker">
 
 ```shell
-docker-compose run --rm web yarn test
+docker compose run --rm web yarn test
 ```
 
 </TabItem>

documentation/docs/contribute/development-guide/04-upgrading.md

@@ -7,7 +7,7 @@ Remember to restart!
 
 Any changes you make to these files will only come into effect after you restart the
 server. If you run the application using containers,
-you need to do `docker-compose build` and then `docker-compose up` to get the changes.
+you need to do `docker compose build` and then `docker compose up` to get the changes.
 
 :::