[taler-docs] branch master updated: DD 027: Sandboxing Taler.

[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 176a262  DD 027: Sandboxing Taler.
176a262 is described below

commit 176a26273817e3204d979bec81f6082fe48998f4
Author: ms <ms@taler.net>
AuthorDate: Mon Feb 7 16:39:23 2022 +0100

    DD 027: Sandboxing Taler.
---
 design-documents/027-sandboxing-taler.rst | 41 +++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

diff --git a/design-documents/027-sandboxing-taler.rst 
b/design-documents/027-sandboxing-taler.rst
new file mode 100644
index 0000000..3958184
--- /dev/null
+++ b/design-documents/027-sandboxing-taler.rst
@@ -0,0 +1,41 @@
+Design Doc 027: Sandboxing all the Taler services. 
+##################################################
+
+.. note::
+
+  This design document is currently a draft, it
+  does not reflect any implementation decisions yet.
+
+Summary
+=======
+
+This document presents a method of deploying all the Taler
+services via one Docker container.
+
+Implementation
+==============
+
+The container is based on Debian Sid, and it installs all
+the services from their Debian packages.  During the build
+process, it creates all the 'static' configuration.  This
+one includes all the .conf-files, the database setup and the
+keying.
+
+Subsequently at the launch step, the system will create all
+the remaining RESTful resources.  Such RESTful resources include
+the merchant instances and all the euFin accounts, both at Sandbox
+and at Nexus.
+
+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?
+
+
+
+
+
+

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