commit e7b5c16ac0d38df83a8c00bff52be56a4bdb4de2
parent 05715df69cd6398b23d06ec7930bbd4f9f047b99
Author: MS <ms@taler.net>
Date: Tue, 8 Nov 2022 15:44:51 +0100
readme
Diffstat:
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/docker/demo/README b/docker/demo/README
@@ -28,7 +28,7 @@ Base image
This image contains a minimal Debian distribution
with ALL the Taler software and its dependencies.
-Navigate to the "images/base" folder, and run the
+Navigate to the "images/base" directory, and run the
following command:
$ docker build --no-cache -t taler_local/taler_base .
@@ -36,7 +36,7 @@ following command:
Composed containers
-------------------
-From this folder, run:
+From this directory, run:
$ docker-compose build
@@ -53,7 +53,23 @@ for an example.
Run
---
-From this folder:
+The following command starts all the services in the background,
+and manages all the restarts (FIXME: observed once, to be confirmed!).
+Run it from this directory:
+
+ $ docker-compose up --remove-orphans -d
+
+On a daemonized setup, live logs can still be seen by running
+the following command from this directory:
+
+ $ docker-compose logs
+
+To stop the services, run the following command from this directory:
+ $ docker-compose stop
+
+To start the services in the foreground, run the following command
+from this directory (no restart is provided):
+
$ docker-compose up --remove-orphans --abort-on-container-exit
Volumes
@@ -69,7 +85,7 @@ the previous step into the Docker volumes. From this directory:
$ ./import-backup.sh $PATH_TO_THE_TAR_FILE
-If data in the volumes needs to be removed, run from this folder:
+If data in the volumes needs to be removed, run from this directory:
$ docker-compose down -v
@@ -86,7 +102,7 @@ The started container should now have all the logs under /logs.
How to test on localhost
========================
-From this folder:
+From this directory:
$ ./test-docker-mvp.sh
