📝 Updated .md files with docker compose V2

open-formulieren · Apr 3, 2024 · b9985bf · b9985bf
1 parent 26940bb
commit b9985bf
Show file tree

Hide file tree

Showing 5 changed files with 11 additions and 11 deletions.
diff --git a/docker/camunda/README.md b/docker/camunda/README.md
@@ -11,7 +11,7 @@ for production usage.
 Start a Camunda instance in your local environment from the parent directory:
 
 ```bash
-docker-compose -f docker-compose.camunda.yml up -d
+docker compose -f docker-compose.camunda.yml up -d
 ```
 
 This brings up the database and Camunda stack. The Camunda cockpit is accessible on

diff --git a/docker/embedding/README.md b/docker/embedding/README.md
@@ -2,14 +2,14 @@
 
 The JS SDK is built to support embedding forms in third party pages, like CMS pages.
 
-The files here and the docker-compose configuration in the parent folder (
+The files here and the `docker compose` configuration in the parent folder (
 `docker-compose.embedding.yml`) exist to test and demo this behaviour.
 
 ## Requirements
 
 To succesfully run an embed test setup, you need:
 
-- docker-compose
+- `docker compose`
 - an Open Forms 2.5.0+ instance, available over HTTPS. E.g. `https://openforms.example.com`
   - the instance must allow CORS requests from `https://localhost:9000`
   - the instance must have `localhost:9000` in the CSRF trusted origins
@@ -19,7 +19,7 @@ Consult the installation/configuration
 [documentation](https://open-forms.readthedocs.io/en/stable/developers/sdk/embedding.html#backend-configuration)
 on how to properly configure your backend for embedding.
 
-## Bring up docker-compose
+## Bring up docker compose
 
 All instructions are relative to the top-level directory.
 
@@ -38,7 +38,7 @@ All instructions are relative to the top-level directory.
 2. Then, bring up the docker services:
 
    ```bash
-   docker-compose -f ./docker/docker-compose.embedding.yml up
+   docker compose -f ./docker/docker-compose.embedding.yml up
    ```
 
 ## Embed test cases

diff --git a/docker/keycloak/README.md b/docker/keycloak/README.md
@@ -6,12 +6,12 @@ an example of an Identity Provider that supports OIDC.
 We include a compose stack for development and CI purposes. This is **NOT** suitable
 for production usage.
 
-## docker-compose
+## docker compose
 
 Start a Keycloak instance in your local environment from the parent directory:
 
 ```bash
-docker-compose -f docker-compose.keycloak.yml up -d
+docker compose -f docker-compose.keycloak.yml up -d
 ```
 
 This brings up Keycloak, the admin interface is accessible at http://localhost:8080/.

diff --git a/docker/objects-apis/README.md b/docker/objects-apis/README.md
@@ -10,7 +10,7 @@ Start an instance in your local environment from the parent directory:
 docker compose -f docker-compose.objects-apis.yml up -d
 ```
 
-Create a super user:
+Create a superuser:
 
 ```bash
 docker compose -f docker-compose.objects-apis.yml exec objecttypes-web src/manage.py createsuperuser

diff --git a/nlx/README.md b/nlx/README.md
@@ -2,7 +2,7 @@
 
 [NLX][NLX] integration is optional.
 
-This directory contains the docker-compose tooling and instructions on how to enable
+This directory contains the `docker compose` tooling and instructions on how to enable
 NLX on the demo network and connect Open Forms services with it.
 
 Ensure you are in the Open Forms repository `nlx` directory for any steps documented
@@ -45,10 +45,10 @@ sudo chmod go-rwx nlx-try-me/pki/certs/internal-cert-key.pem
 
 ## Running the NLX stack
 
-Navigate to this (`nlx`) directory and start the components using docker-compose:
+Navigate to this (`nlx`) directory and start the components using `docker compose`:
 
 ```bash
-docker-compose up
+docker compose up
 ```
 
 and follow the rest of the guide at the