taler-deployment

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

commit 05715df69cd6398b23d06ec7930bbd4f9f047b99
parent 6db359f4cf48899be194d9771176293f2d27e919
Author: MS <ms@taler.net>
Date:   Tue,  8 Nov 2022 15:35:58 +0100

readme

Diffstat:
Mdocker/demo/README | 27++++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)

diff --git a/docker/demo/README b/docker/demo/README @@ -19,6 +19,9 @@ of Docker. How to compile ============== +The base image (not managed by the docker-compose setup) and +all the other images must be compiled. + Base image ---------- @@ -47,32 +50,34 @@ Export the env variable TALER_DEPLOYMENT_CONFIG to an absolute path of a configuration file. See config/deployment.conf for an example. +Run +--- + +From this folder: + $ docker-compose up --remove-orphans --abort-on-container-exit + Volumes ------- -Data is kept into Docker volumes. From this directory, -run the following command to export database, key material, and logs: +Data is kept into Docker volumes. To export database, key +material, and logs, run the following command from this directory. $ ./backup.sh The following command imports the TAR backup from the previous step into the Docker volumes. From this directory: - $ ./import-backup.sh + $ ./import-backup.sh $PATH_TO_THE_TAR_FILE -If data needs to be removed, from this folder: - $ docker-compose down -v - -Run ---- +If data in the volumes needs to be removed, run from this folder: -From this folder: - $ docker-compose up --remove-orphans --abort-on-container-exit + $ docker-compose down -v Logs ---- -Newest rotated logs can be seen by: +Newest rotated logs can be seen by the following command, +from any directory: $ docker run -v hybrid_talerlogs:/logs -it taler_local/taler_base /bin/bash