[taler-docs] branch master updated: DD 027

[gnunet]

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

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 0cdfa91  DD 027
0cdfa91 is described below

commit 0cdfa91271c7cf348276e18d775f9766f76ae699
Author: ms <ms@taler.net>
AuthorDate: Mon Feb 7 17:10:39 2022 +0100

    DD 027
---
 design-documents/027-sandboxing-taler.rst | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)

diff --git a/design-documents/027-sandboxing-taler.rst 
b/design-documents/027-sandboxing-taler.rst
index c1db20a..a2b60fe 100644
--- a/design-documents/027-sandboxing-taler.rst
+++ b/design-documents/027-sandboxing-taler.rst
@@ -26,16 +26,30 @@ the remaining RESTful resources.  Such RESTful resources 
include
 the merchant instances and all the euFin accounts, both at Sandbox
 and at Nexus.
 
+The sandbox will serve one HTTP base URL and make any service
+reachable at $baseUrl/$service.  For example, the exchange base
+URL will be "$baseUrl/exchange".
+
+The sandbox allows to configure:
+
+- which host it binds to, typically localhost+port.
+- which host is being reverse proxied to the sandbox.  This
+  helps to generate valid URIs of services.
+
+All the other values will be hard-coded in the preparation.
+
 Open questions
 ==============
 
 - How to collect the static configuration values?
+
 - How to persist, at build time, the information
   needed later at launch time to create the RESTful
   resources?
 
-
-
-
-
-
+- Should we at this iteration hard-code passwords too?
+  With generated passwords, (1) it won't be possible to
+  manually log-in to services, (2) it won't be possible
+  to write the exchange password for Nexus in the conf.
+  Clearly, that's a problem when the sandbox is served
+  to the outside.

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