[taler-deployment] 02/02: netzbon readme

[gnunet]

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

ms pushed a commit to branch master
in repository deployment.

commit 86e8d266db11c5b923a96d85861b31197659fbd1
Author: MS <ms@taler.net>
AuthorDate: Tue Mar 14 17:56:53 2023 +0100

    netzbon readme
---
 netzbon/README | 59 ++++++++++++++++++++--------------------------------------
 1 file changed, 20 insertions(+), 39 deletions(-)

diff --git a/netzbon/README b/netzbon/README
index 17ecee8..d74f8a5 100644
--- a/netzbon/README
+++ b/netzbon/README
@@ -1,58 +1,40 @@
 This directory contains a set of scripts aiming at deploying
 Taler by asking questions to the user and providing the values
-both to the various Taler subsystems (LibEufin, Exchange,
-Merchant, ..) and to Nginx.
+both to the various Taler subsystems (LibEufin, Exchange, Merchant,
+..) and to Nginx.
 
 main.sh is the main script that asks the questions and
 puts the answers in environment variables and/or replaces them
 into Nginx configuration file(s).
 
-In the current version, the main script does ONLY support
-LibEuFin.
-
-FIXMEs.
-
-0.  Start LibEuFin via SystemD.
-
-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.
-
-
 Concept
 =======
 
-The different stages of the installation have their own shell scripts, driven
-by the 'main.sh' 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 of the installation have their own shell
+scripts, driven by the 'main.sh' 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 'main.sh' script also prompts the
-user for key inputs, in particular:
+The different stages communicate via environment variables which
+they may consume or export for future stages.  The 'main.sh' script
+prompts the user for the following inputs:
 
 * 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 master password to set for the administrative Web interface
 
-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 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
+[NOTE: they do for the DB config], 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).
 
-
 Objective
 =========
 
@@ -64,14 +46,13 @@ all of the components:
 * exchange with denominations, fees (all zero) and credentials for the 
libeufin-nexus
 * merchant backend with the master key of the exchange for the target currency
 
-
 Future
 ======
 
 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.
+locally (in a system that is online).  Future deployments should aim at moving
+the offline keys in a offline system.
 
 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.
+only have libeufin-nexus between libeufin-sandbox and exchange. In the future,
+nexus will also communicate with an external bank. 

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