[Top][All Lists]

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

[taler-deployment] branch master updated: target

From: gnunet
Subject: [taler-deployment] branch master updated: target
Date: Thu, 02 Mar 2023 15:01:46 +0100

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

grothoff pushed a commit to branch master
in repository deployment.

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

commit f39449ac59bf240a66daf41f7814dc969011adbb
Author: Christian Grothoff <>
AuthorDate: Thu Mar 2 15:00:09 2023 +0100

 netzbon/README | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)

diff --git a/netzbon/README b/netzbon/README
index ad25bf9..17ecee8 100644
--- a/netzbon/README
+++ b/netzbon/README
@@ -19,3 +19,59 @@ TODOs.
 0.  Provide exchange sub-script.
 1.  Provide merchant sub-script.
 2.  Replace answers into the Nginx config.
+This directory contains shell scripts to make the installation of GNU Taler
+as easy as possible.
+The different stages of the installation have their own shell scripts, driven
+by the '' master script. Splitting up the process into the main stages
+should make it easy to resume if any particular step fails for any reason.
+The different stages communicate via environment variables which they may
+consume or export for future stages.  The '' script also prompts the
+user for key inputs, in particular:
+* the main domain name (subdomains may be created automatically)
+* the name of the currency
+* the master password(s) to set for the administrative Web interface(s)
+The setup is fundamentally based on the Debian packages.  The scripts should
+do the minimal amount necessary to get GNU Taler to work on top of what the
+Debian packages provide. If we can move logic into a Debian package, we should.
+However, the Debian packages MUST install non-interactively, so site-specific
+inputs MUST be done by the shell scripts.
+The shell scripts should be kept simple, and for example use default
+configuration(s) from the Debian packages and replace values with 'sed'
+instead of generating complete configurations themselves (where possible,
+so in particular for the reverse HTTPS proxy configuration).
+The goal is not to only setup the Debian packages, but to also configure
+all of the components:
+* libeufin-sandbox with an account for the administrator and the exchange
+* libeufin-nexus with access to the exchange account and Taler facade
+* exchange with denominations, fees (all zero) and credentials for the 
+* merchant backend with the master key of the exchange for the target currency
+For now, it is assumed that the taler-exchange-offline functionality is run
+locally (online). It should, however, be kept in mind that we probably want to
+modify the script to keep the offline keys offline in the future.
+For now, we do not integrate the currency conversion / cash out logic and
+only have the nexus between sandbox and exchange. In the future, we will want
+to support nexus talking to an external bank.

To stop receiving notification emails like this one, please contact

reply via email to

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