gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-deployment] branch master updated: document manual reserve creati


From: gnunet
Subject: [taler-deployment] branch master updated: document manual reserve creation
Date: Thu, 23 Feb 2023 00:50:45 +0100

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new 4f7f4a5  document manual reserve creation
4f7f4a5 is described below

commit 4f7f4a5fe02f8f5869673ec61f2b960a4ba62c58
Author: Florian Dold <florian@dold.me>
AuthorDate: Thu Feb 23 00:50:33 2023 +0100

    document manual reserve creation
---
 sandcastle/README | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/sandcastle/README b/sandcastle/README
index 9d0e7ac..c79fd6e 100644
--- a/sandcastle/README
+++ b/sandcastle/README
@@ -72,6 +72,23 @@ $ docker-compose up $image-name
 'bank', 'exchange', 'merchant', 'talerdb' are valid values
 for $image-name.
 
+Enabling tipping
+================
+
+The following command manually creates a tipping reserve:
+
+$ taler-harness deployment tip-topup --merchant-url 
https://backend.demo.taler.net/instances/survey/ 
--merchant-apikey=$MERCHANT_APIKEY --bank-access-url 
https://bank.demo.taler.net/demobanks/default/access-api/ --wire-method=iban 
--amount=KUDOS:5000 --bank-account=survey-at-sandbox 
--bank-password=$SURVEY_SECRET --exchange-url https://exchange.demo.taler.net/
+
+The status of tipping reserves can be checked via:
+
+$ taler-harness deployment tip-status --merchant-url 
https://backend.demo.taler.net/instances/survey/ 
--merchant-apikey=$MERCHANT_APIKEY
+
+To purge all non-funded tipping reserves, run:
+
+$ taler-harness deployment tip-cleanup --merchant-url 
https://backend.demo.taler.net/instances/survey/ 
--merchant-apikey=$MERCHANT_APIKEY
+
+
+
 How to run
 ==========
 

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]