gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: remove obsolete


From: gnunet
Subject: [taler-docs] branch master updated: remove obsolete
Date: Sun, 13 Nov 2022 12:42:25 +0100

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 71c39ef  remove obsolete
71c39ef is described below

commit 71c39efddf4f424760eec7b1503453dff4db77c9
Author: MS <ms@taler.net>
AuthorDate: Sun Nov 13 12:41:51 2022 +0100

    remove obsolete
---
 taler-developer-manual.rst | 43 +------------------------------------------
 1 file changed, 1 insertion(+), 42 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 0a3b16f..4bb0315 100644
--- 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:

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]