diff options
| -rw-r--r-- | design-documents/027-sandboxing-taler.rst | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/design-documents/027-sandboxing-taler.rst b/design-documents/027-sandboxing-taler.rst new file mode 100644 index 00000000..39581842 --- /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? + + + + + + |