[taler-deployment] branch master updated: readme

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new 101ea5c  readme
101ea5c is described below

commit 101ea5ccf429bcd1e239038254f7ad97065de4f0
Author: MS <ms@taler.net>
AuthorDate: Wed Oct 19 16:58:33 2022 +0200

    readme
---
 docker/hybrid/README | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/docker/hybrid/README b/docker/hybrid/README
index 8ec84e3..60c1419 100644
--- a/docker/hybrid/README
+++ b/docker/hybrid/README
@@ -30,11 +30,11 @@ following command:
 
   $ docker build --no-cache -t taler_local/taler_base .
 
-Compose
--------
+Composed containers
+-------------------
 
 From this folder, run:
-  $ docker-compose down -v # deletes state from previous runs.
+
   $ docker-compose build
 
 How to run
@@ -57,14 +57,17 @@ and postgresql data.
 
 The environment variable TALER_DEPLOYMENT_LOGS controls
 where on the host's filesystem the logs get stored.  It defaults
-to ~/taler-logs, and contains exchange, libeufin, and postgresql
-data.  NOTE: Postgres needs permissions to write in
-TALER_DEPLOYMENT_LOGS because it runs as the 'postgres' user
-(uid=999).
+to ~/taler-logs and will be created by Docker - owned by "root:root" -
+if it's not found.  NOTE: the 'postgres' user (uid=999) needs
+write access to TALER_DEPLOYMENT_LOGS, in order to log from
+the database container.
 
 Run
 ---
 
+Only if stale data needs to be removed, from this folder run:
+  $ docker-compose down -v # deletes state from previous runs.
+
 From this folder, run:
   $ docker-compose up --remove-orphans --abort-on-container-exit
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.