Using docker compose instead of docker-compose in scripts

Author: rolljee

.ci/scripts/run-monkey-tests.sh

@@ -15,16 +15,16 @@ npm install --unsafe-perm
 
 if [ "$REBUILD" == "true" ];
 then
-  docker-compose -f ./.ci/test-cluster.yml run kuzzle_node_1 npm rebuild
+  docker compose -f ./.ci/test-cluster.yml run kuzzle_node_1 npm rebuild
 fi
 
 npm run build-ts
 
 echo "[$(date)] - Starting Kuzzle Cluster..."
 
-trap 'docker-compose -f ./.ci/test-cluster.yml logs' err
+trap 'docker compose -f ./.ci/test-cluster.yml logs' err
 
-docker-compose -f ./.ci/test-cluster.yml up -d
+docker compose -f ./.ci/test-cluster.yml up -d
 
 # don't wait on 7512: nginx will accept connections far before Kuzzle does
 KUZZLE_PORT=17510 ./bin/wait-kuzzle

.ci/scripts/run-test-cluster.sh

@@ -16,16 +16,16 @@ npm install
 
 if [ "$REBUILD" == "true" ];
 then
-  docker-compose -f ./.ci/test-cluster.yml run kuzzle_node_1 npm rebuild
+  docker compose -f ./.ci/test-cluster.yml run kuzzle_node_1 npm rebuild
 fi
 
 npm run build-ts
 
 echo "[$(date)] - Starting Kuzzle Cluster..."
 
-trap 'docker-compose -f ./.ci/test-cluster.yml logs' err
+trap 'docker compose -f ./.ci/test-cluster.yml logs' err
 
-docker-compose -f ./.ci/test-cluster.yml up -d
+docker compose -f ./.ci/test-cluster.yml up -d
 
 # don't wait on 7512: nginx will accept connections far before Kuzzle does
 KUZZLE_PORT=17510 ./bin/wait-kuzzle

.github/actions/build-and-run-kuzzle/action.yml

@@ -17,15 +17,15 @@ runs:
       shell: bash
     - run: |
         export KUZZLE_IMAGE=${{ inputs.KUZZLE_IMAGE }}
-        docker-compose -f ./.ci/services.yml up -d
+        docker compose -f ./.ci/services.yml up -d
       shell: bash
     - run: |
-        trap 'docker-compose -f ./.ci/services.yml logs' err
+        trap 'docker compose -f ./.ci/services.yml logs' err
 
         export MAX_TRIES=60
         ./bin/wait-kuzzle
 
         trap - err
       shell: bash
-    - run: docker-compose -f ./.ci/services.yml down
+    - run: docker compose -f ./.ci/services.yml down
       shell: bash

CONTRIBUTING.md

@@ -25,7 +25,7 @@ We use most of the [NPM Coding Style](https://www.w3resource.com/npm/npm-coding-
 
 ## Tools
 
-For development only, we built a specific docker-compose file: `docker-compose.yml`. You can use it to profile, debug, test a variable on the fly, add breakpoints and so on, thanks to [chrome-devtools](https://developer.chrome.com/devtools).  
+For development only, we built a specific docker- ompose file: `docker-compose.yml`. You can use it to profile, debug, test a variable on the fly, add breakpoints and so on, thanks to [chrome-devtools](https://developer.chrome.com/devtools).  
 Check the logs at the start of Kuzzle using the development docker image to get the appropriate debug URL.
 
 How to run the development stack (needs Docker 1.10+ and Docker Compose 1.8+):
@@ -36,7 +36,7 @@ git clone git@github.com:kuzzleio/kuzzle.git
 cd kuzzle
 
 # Start a kuzzle cluster with development tools enabled
-docker-compose up
+docker compose up
 ```
 
 ### ENOSPC error
@@ -98,7 +98,7 @@ See our [plugins documentation](https://docs.kuzzle.io/core/2/plugins/)
 ### Using docker, with Kuzzle running in Docker
 
 ```bash
-$ docker-compose up -d
+$ docker compose up -d
 
 # Wait for Kuzzle stack to be up, and start the entire test suite (long)
 $ npm run test

README.md

@@ -142,5 +142,5 @@ Run the following command to install all the dependencies in your container:
 npm run docker:install
 ```
 
-finally run the command `docker-compose up` to launch your kuzzle stack.
+finally run the command `docker compose up` to launch your kuzzle stack.
 

doc/2/guides/getting-started/deploy-your-application/index.md

@@ -150,7 +150,7 @@ $ ssh <user>@<server-ip>
 
 [...]
 
-$ docker-compose -f deployment/docker-compose.yml up -d
+$ docker compose -f deployment/docker-compose.yml up -d
 ```
 
 Your Kuzzle application is now up and running on port 7512!

vagrant/kuzzle.sh

@@ -10,4 +10,4 @@
 
 echo "launching kuzzle"
 cd /vagrant
-docker-compose -p kuzzle up -d
+docker compose -p kuzzle up -d