[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: explain merchant default auth
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: explain merchant default auth |
Date: |
Fri, 21 May 2021 20:01:56 +0200 |
This is an automated email from the git hooks/post-receive script.
ms pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 8ff9434 explain merchant default auth
8ff9434 is described below
commit 8ff943438779ecde4f04c12a9f7e3505540eea5a
Author: MS <ms@taler.net>
AuthorDate: Fri May 21 20:01:53 2021 +0200
explain merchant default auth
---
core/api-merchant.rst | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index 56a9187..e15ab03 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -34,7 +34,12 @@ This is useful when multiple businesses want to share the
same payment
infrastructure.
Merchant backends have one special ``default`` instance. This ``default``
-instance is used when no explicit instance is specified.
+instance is used when no explicit instance is specified. Despite its name,
+this instance must be created after the installation. In case *no* default
+instance is found - or its credentials got lost -, the administrator can use
+the default instance's rights by resorting on the ``--auth`` command line
option,
+or by restarting the service by providing a environment variable called
+``TALER_MERCHANT_TOKEN``.
Each instance (default and others) has a base URL. The resources under
this base URL are divided into to categories:
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: explain merchant default auth,
gnunet <=