gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-deployment] 02/02: README


From: gnunet
Subject: [taler-deployment] 02/02: README
Date: Thu, 06 Oct 2022 12:02:52 +0200

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

ms pushed a commit to branch master
in repository deployment.

commit 95d0db047f482a3a81dd77cc99521df2e91ecb3a
Author: MS <ms@taler.net>
AuthorDate: Thu Oct 6 12:02:42 2022 +0200

    README
---
 docker/hybrid/README | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)

diff --git a/docker/hybrid/README b/docker/hybrid/README
new file mode 100644
index 0000000..1ae6141
--- /dev/null
+++ b/docker/hybrid/README
@@ -0,0 +1,53 @@
+Description
+===========
+
+This setup orchestrates the following containers:
+
+1.  Banking (libEufin)
+2.  Shop(s)
+3.  Payment service provider (Taler exchange and helpers)
+
+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.
+
+How to compile
+==============
+
+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
+following command:
+
+  $ docker build --no-cache -t taler_local/taler_base .
+
+Compose
+-------
+
+From this folder, run:
+  $ docker-compose down # deletes state from previous runs.
+  $ docker-compose build
+
+How to run
+==========
+
+From this folder, run:
+  $ docker-compose up
+
+How to test
+===========
+
+From this folder, run:
+  
+  $ ./test-docker-mvp.sh
+
+The above test registers a new bank account to libEufin,
+withdraw coins and spend them directly at the merchant backend.

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]