diff options
| author | Florian Dold <florian@dold.me> | 2023-09-04 18:59:33 +0200 |
|---|---|---|
| committer | Florian Dold <florian@dold.me> | 2023-09-04 18:59:33 +0200 |
| commit | 90669a5fb3178025d38258616194f91812b02764 (patch) | |
| tree | d16ce1968f14cb44f62a9f9d310779707eeef963 /taler-auditor-manual.rst | |
| parent | 7a1ddc0871176ba1e5adf7eb55c7bea39e80f1c7 (diff) | |
| download | docs-90669a5fb3178025d38258616194f91812b02764.tar.gz docs-90669a5fb3178025d38258616194f91812b02764.tar.bz2 docs-90669a5fb3178025d38258616194f91812b02764.zip | |
various doc fixes
Diffstat (limited to 'taler-auditor-manual.rst')
| -rw-r--r-- | taler-auditor-manual.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 6a7b9ea4..feaf7783 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -582,7 +582,7 @@ 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 as illustrated in the following figure: -.. image:: replication.png +.. image:: images/replication.png First, the exchange should use standard PostgreSQL replication features to enable the auditor to obtain a full copy of the exchange's database. @@ -968,7 +968,7 @@ The auditor's database The database scheme used by the exchange looks as follows: -.. image:: auditor-db.png +.. image:: images/auditor-db.png Invariants checked by the auditor |