summaryrefslogtreecommitdiff
path: root/docker
diff options
context:
space:
mode:
authorMS <ms@taler.net>2022-11-20 19:59:56 +0100
committerMS <ms@taler.net>2022-11-20 19:59:56 +0100
commita06a4a5a6ddd06e2a71283b8c15486312ddd3b3e (patch)
tree9f6e84798bd0877709c6a8528a21bb72911125a9 /docker
parent23d7beb2af2eab2f2b754e0c8ee10a1ccce84d27 (diff)
downloaddeployment-a06a4a5a6ddd06e2a71283b8c15486312ddd3b3e.tar.gz
deployment-a06a4a5a6ddd06e2a71283b8c15486312ddd3b3e.tar.bz2
deployment-a06a4a5a6ddd06e2a71283b8c15486312ddd3b3e.zip
readme: data removal
Diffstat (limited to 'docker')
-rw-r--r--docker/demo/README33
1 files changed, 23 insertions, 10 deletions
diff --git a/docker/demo/README b/docker/demo/README
index 2ba2f1f..15f5041 100644
--- a/docker/demo/README
+++ b/docker/demo/README
@@ -8,18 +8,9 @@ This setup orchestrates the following containers:
3. Payment service provider (Taler exchange and helpers)
4. Database
-Note: one stratagem was however needed to make it work.
-The merchant container needs to redirect requests to
-"localhost:$EXCHANGE_PORT_AT_HOST" to the Docker network,
-in order to actually reach the exchange. That fixes the
-"/pay" handling, since wallets suggest the exchange base URL
-but have a different network view, because they run outside
-of Docker.
-
FIXME (#7463): the current version requires the user to manually
point the bank SPA to any backend not being served at bank.demo.taler.net.
-
How to compile
==============
@@ -116,7 +107,7 @@ for debugging.
On a daemonized setup, live logs can still be seen by running
the following command from this directory:
- $ docker-compose logs
+ $ docker-compose logs --tail=$NUM --follow [container-name]
To stop the services, run the following command from this directory:
$ docker-compose stop
@@ -141,8 +132,30 @@ the previous step into the Docker volumes. From this directory:
If data in the volumes needs to be removed, run from this directory:
+
+Data removal
+------------
+
+Data can be classified between Taler (DBs, keys, logs), and Docker specific
+(dangling images, volumes, stopped containers). Most of Taler data is found
+in 'volumes', and can be removed in the following way:
+
+ # From this directory.
$ docker-compose down -v
+Note: the current version does not store config files into volumes, but in
+services' containers.
+
+Use the following command to remove stopped containers, dangling images
+and build cache, and unused networks. After its return, the Taler sandbox
+can be run again without rebuilding it.
+
+ $ docker system prune
+
+Disk usage can be monitored by the command:
+
+ $ docker system df
+
Logs
----