taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 71c39efddf4f424760eec7b1503453dff4db77c9
parent 44f5e5c57e3f28b6034dd59151bcf4cea47642b4
Author: MS <ms@taler.net>
Date:   Sun, 13 Nov 2022 12:41:51 +0100

remove obsolete

Diffstat:
Mtaler-developer-manual.rst | 43+------------------------------------------
1 file changed, 1 insertion(+), 42 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst @@ -443,47 +443,6 @@ by Buildbot. The results are then published at ``https://lcov.taler.net/``. -Service Checker ---------------- - -The user ``demo-checker`` runs periodic checks to see if all the -``*.demo.taler.net`` services are up and running. It is driven by -Buildbot, and can be bootstrapped as follows. - -.. code-block:: console - - # Log-in as the 'demo-checker' user - - $ cd $HOME - $ git clone git://git.taler.net/deployment - $ ./deployment/bootstrap-demochecker - - # If the previous step worked, the setup is - # complete and the Buildbot worker can be started. - - $ buildbot-worker start worker/ - - -Tipping reserve top-up ----------------------- - -Both 'test' and 'demo' setups get their tip reserve topped up -by a Buildbot worker. The following steps get the reserve topper -prepared. - -.. code-block:: console - - # Log-in as <env>-topper, with <env> being either 'test' or 'demo' - - $ git clone git://git.taler.net/deployment - $ ./deployment/prepare-reservetopper <env> - - # If the previous steps worked, then it should suffice to start - # the worker, with: - - $ buildbot-worker start worker/ - - Producing auditor reports ------------------------- @@ -496,7 +455,7 @@ prepared. # Log-in as <env>-auditor, with <env> being either 'test' or 'demo' $ git clone git://git.taler.net/deployment - $ ./deployment/prepare-auditorreporter <env> + $ ./deployment/buildbot/bootstrap-scripts/prepare-auditorreporter <env> # If the previous steps worked, then it should suffice to start # the worker, with: