Update READMEs to use docker compose instead of docker-compose

Author: dersmon

desktop/README.md

@@ -64,7 +64,7 @@ To execute **integration test with Field Hub**, run
 $ npm run test:hub-integration --prefix desktop
 ```
 
-The Field Hub integration tests require installed Docker and docker-compose.
+The Field Hub integration tests require installed Docker.
 
 ## Packaging
 

desktop/test/hub-integration/README.md

@@ -1,3 +1,3 @@
 # Field Hub integration tests
 
-These integration tests require Docker/docker-compose to be installed on your system. A release version of Field Hub will be pulled from the Github container registry, see [docker-compose.yml](docker-compose.yml).
+These integration tests require Docker to be installed on your system. A release version of Field Hub will be pulled from the Github container registry, see [docker-compose.yml](docker-compose.yml).

publication/README.md

@@ -18,7 +18,7 @@ Field Publication relies on several services:
 
 The [docker-compose.yml](docker-compose.yml) defines all three services for development. For starting the dockerized services run:
 ```
-docker-compose up
+docker compose up
 ```
 
 ## 2. Running the setup

server/README.md

@@ -30,13 +30,13 @@ If you change the default CouchDB credentials in your `.env` file, make sure to
 Start a dockerized CouchDB:
 
 ```bash
-docker-compose up
+docker compose up
 ```
 
 Or, if you want to run docker in the background:
 
 ```bash
-docker-compose up -d
+docker compose up -d
 ```
 
 ### Phoenix Server

server/deployment_example/README.md

@@ -50,7 +50,7 @@ _Note: if you want the files to be put somewhere else, you can do that by updati
 Run the application from the directory containing both files with:
 
 ```
-docker-compose up
+docker compose up
 ```
 
 This should run the application in the foreground and display logs for both services. The services can also be viewed in your webbrowser at port 80 (FieldHub service) and port 5984 (CouchDB service). For CouchDB's webinterface go to (..):5984/_utils/. 
@@ -79,13 +79,13 @@ To run the application in production, you should do (atleast) 3 things:
 Afterwards stop and delete all previously created test containers.
 
 ```
-docker-compose down -v
+docker compose down -v
 ```
 
 Finally, we want to start everything in the background, using the detached `-d` option.
 
 ```
-docker-compose up -d
+docker compose up -d
 ```
 
 If you want to see which containers are now running there are several commands.