taler-docs

commit 8c0768d06149eddee1167e84cc3f94201c6d0be2
parent 00566931b40249cb4adb5b301db383311880625d
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Sat, 22 Mar 2025 14:29:51 +0100

tutorial with default merchant http port

Diffstat:
M
taler-merchant-manual.rst
 | 
12
++++++------

1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -474,13 +474,13 @@ address. If frontend and backend run within the same operating system, the
 use of a UNIX domain socket is recommended to avoid accidentally exposing
 the backend to the network.
 
-To run the Taler backend on TCP port 8888, use:
+To run the Taler backend on TCP port 9966 (the default), use:
 
 .. code-block:: ini
 
    [MERCHANT]
    SERVE = tcp
-   PORT = 8888
+   PORT = 9966
 
 .. note::
 
@@ -667,7 +667,7 @@ The following is an example for a complete backend configuration:
 
    [merchant]
    SERVE = TCP
-   PORT = 8888
+   PORT = 9966
    DATABASE = postgres
 
    [merchantdb-postgres]
@@ -731,7 +731,7 @@ If everything worked as expected, the command
 
 .. code-block:: console
 
-   $ wget -O - http://localhost:8888/config
+   $ wget -O - http://localhost:9966/config
 
 should return some basic configuration status data about the service.
 
@@ -838,10 +838,10 @@ You can then create the instance using:
 
 .. code-block:: console
 
-   $ wget --post-file=instance.json http://localhost:8888/management/instances
+   $ wget --post-file=instance.json http://localhost:9966/management/instances
 
 The base URL for the instance will then be
-``http://localhost:8888/instances/default``.  You can create additional
+``http://localhost:9966/instances/default``.  You can create additional
 instances by changing the ``id`` value to identifies other than ``default``.
 
 Endpoints to modify (reconfigure), permanently disable (while keeping the data)