summaryrefslogtreecommitdiff
path: root/taler-auditor-manual.rst
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-01-15 13:27:41 +0100
committerChristian Grothoff <christian@grothoff.org>2021-01-15 13:27:41 +0100
commit014c1cd4e5160e2383927e74970a4e0d794584a1 (patch)
tree5938608a895949456436eb52de7f14cec070de1f /taler-auditor-manual.rst
parent007421e881da19eddaaab61484a69e7837d23b0d (diff)
downloaddocs-014c1cd4e5160e2383927e74970a4e0d794584a1.tar.gz
docs-014c1cd4e5160e2383927e74970a4e0d794584a1.tar.bz2
docs-014c1cd4e5160e2383927e74970a4e0d794584a1.zip
include overview picture
Diffstat (limited to 'taler-auditor-manual.rst')
-rw-r--r--taler-auditor-manual.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index adfb57a..66e3d05 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -438,7 +438,10 @@ Database
--------
The next key step for the auditor is to configure replication of the
-*exchange*'s database in-house. This should be performed in two steps.
+*exchange*'s database in-house. This should be performed in two steps
+as illustrated in the following figure:
+
+.. image:: replication.png
First, the exchange should use standard Postgres replication features to
enable the auditor to obtain a full copy of the exchange's database.