summaryrefslogtreecommitdiff
path: root/design-documents/027-sandboxing-taler.rst
diff options
context:
space:
mode:
Diffstat (limited to 'design-documents/027-sandboxing-taler.rst')
-rw-r--r--design-documents/027-sandboxing-taler.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/design-documents/027-sandboxing-taler.rst b/design-documents/027-sandboxing-taler.rst
index c1e52939..1a09baf4 100644
--- a/design-documents/027-sandboxing-taler.rst
+++ b/design-documents/027-sandboxing-taler.rst
@@ -1,5 +1,5 @@
-Design Doc 027: Sandboxing all the Taler services.
-##################################################
+DD 27: Sandboxing all the Taler services
+########################################
.. note::
@@ -80,7 +80,7 @@ Open questions
- How to collect the static configuration values?
- => Via a configuration file that you pass to the container via
- a mounted directory (=> `-v $MYCONFIG:/sandboxconfig`)
+ a mounted directory (=> ``-v $MYCONFIG:/sandboxconfig``)
- If we don't pass any config, the container should have
sane defaults
- This is effectively a "meta configuration", because it will
@@ -108,7 +108,7 @@ Open questions
- future/optional: we *might* allow connection to an external postgresql database as well
- How are services supervised?
-
+
- SystemD? gnunet-arm? supervisord? something else?
- SystemD does not work well inside containers
@@ -134,7 +134,7 @@ Open questions
- Might be simpler if we disallow this
- How do we handle TLS
-
+
- Do we always do HTTPs in the sandbox container?
- We need to think about external and internal requests
to the sandbox