taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

commit 66cdd18ca62f79af1ae1e0b2beb40ef667818b2d
parent d6a431f46cd8f7f3f5857594254b32975b575b36
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Mon, 14 Nov 2016 01:02:34 +0100

TODO containers

Diffstat:
Adocker/TODO | 22++++++++++++++++++++++
1 file changed, 22 insertions(+), 0 deletions(-)

diff --git a/docker/TODO b/docker/TODO @@ -0,0 +1,22 @@ +Missing containers: + +- "standalone" ones: they actually *run* the + service and may also link to configuration on + the host machine when they are launched. + +- frontends +- bank +- postgres (as a running service) + +Missing compositions: + +Ideally, the Docker setting should instantiate two +Taler flavours: + +- Self-contained testing: all components ready to be + tested by the automated clicker, AKA they are a replacement + for what runs at *.{test,demo}.taler.net + +- Ready-to-ship: a composition that instantiates a fully + operational exchange or merchant, according to the customer + needs.