update docker compose for changed database docker

docker-compose.override.yml

@@ -144,16 +144,15 @@ services:
     #  Due to problems with the volume caching the built files
     #  we changed this to test build. This keeps the service running.
     # name the image so that it cannot be found in a DockerHub repository, otherwise it will not be built locally from the 'dockerfile' but pulled from there
-    image: gradido/database:local-test_up
+    image: gradido/database:local-up
     build:
-      target: test_up
+      target: up
     environment:
       - NODE_ENV="development"
     volumes:
       # This makes sure the docker container has its own node modules.
       # Therefore it is possible to have a different node version on the host machine
       - database_node_modules:/app/node_modules
-      - database_build:/app/build
       # bind the local folder to the docker to allow live reload
       - ./database:/app
 
@@ -239,6 +238,5 @@ volumes:
   federation_config_node_modules:
   federation_config_build:
   database_node_modules:
-  database_build:
   dlt-database_node_modules:
   dlt-database_build:

docker-compose.reset.yml

@@ -12,10 +12,10 @@ services:
   ########################################################
   database:
     # name the image so that it cannot be found in a DockerHub repository, otherwise it will not be built locally from the 'dockerfile' but pulled from there
-    image: gradido/database:local-production_reset
+    image: gradido/database:local-reset
     build:
       context: ./database
-      target: production_reset
+      target: reset
     depends_on:
       - mariadb
     networks:

docker-compose.test.yml

@@ -68,10 +68,10 @@ services:
   # DATABASE #############################################
   ########################################################
   database:
-    image: gradido/database:test_up
+    image: gradido/database:up
     build:
       context: ./database
-      target: test_up
+      target: up
     environment:
       - NODE_ENV=test
   #  restart: always # this is very dangerous, but worth a test for the delayed mariadb startup at first run

docker-compose.yml

@@ -218,10 +218,10 @@ services:
   ########################################################
   database:
     # name the image so that it cannot be found in a DockerHub repository, otherwise it will not be built locally from the 'dockerfile' but pulled from there
-    image: gradido/database:local-production_up
+    image: gradido/database:local-up
     build:
       context: ./database
-      target: production_up
+      target: up
     depends_on:
       - mariadb
     networks: