From d292952768ba971b9d9d7393980aaef2b3b45449 Mon Sep 17 00:00:00 2001
From: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
Date: Thu, 23 Feb 2023 17:23:46 +0100
Subject: [PATCH] docu regarding docker-compose exec does not work - use docker
 exec

---
 backend/README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/backend/README.md b/backend/README.md
index a70c4a10d..4ce74dc40 100644
--- a/backend/README.md
+++ b/backend/README.md
@@ -89,7 +89,7 @@ backend is running:
 
 ```bash
 # in main folder while docker-compose is running
-$ docker-compose exec backend yarn run db:migrate init
+$ docker exec backend yarn run db:migrate init
 ```
 
 {% endtab %}
@@ -116,18 +116,18 @@ In another terminal run:
 
 ```bash
 # in main folder while docker-compose is running
-$ docker-compose exec backend yarn run db:seed
+$ docker exec backend yarn run db:seed
 ```
 
 To reset the database run:
 
 ```bash
 # in main folder while docker-compose is running
-$ docker-compose exec backend yarn run db:reset
+$ docker exec backend yarn run db:reset
 # you could also wipe out your neo4j database and delete all volumes with:
 $ docker-compose down -v
 # if container is not running, run this command to set up your database indeces and contstraints
-$ docker-compose exec backend yarn run db:migrate init
+$ docker exec backend yarn run db:migrate init
 ```
 
 {% endtab %}
@@ -170,7 +170,7 @@ To run the migration:
 
 ```bash
 # in main folder while docker-compose is running
-$ docker-compose exec backend yarn run db:migrate up
+$ docker exec backend yarn run db:migrate up
 ```
 
 {% endtab %}
@@ -206,7 +206,7 @@ Run the unit tests:
 
 ```bash
 # in main folder while docker-compose is running
-$ docker-compose exec backend yarn run test
+$ docker exec backend yarn run test
 ```
 
 {% endtab %}