commit 7a937ebaf0966e6940d586021a4a28686b004281
parent dc84dc2fdbee220db6a160267bd563a517fdf550
Author: buckE <buckE@disroot.org>
Date: Tue, 23 Jun 2020 05:55:25 +0000
more added `s
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/developers-manual.rst b/developers-manual.rst
@@ -324,7 +324,7 @@ Here are some highlights:
- The WORKER is the config that that lives on a shell account on a localhost (taler.net), where this host has buildbot-worker installed. The WORKER executes the commands that perform all end-functions of buildbot.
-- The WORKER running buildbot-worker receives these commands by authenticating and communicating with the buildbot server using parameters that were specified when the worker was created in that shell account with the `buildbot-worker` command.
+- The WORKER running buildbot-worker receives these commands by authenticating and communicating with the buildbot server using parameters that were specified when the worker was created in that shell account with the ``buildbot-worker`` command.
- The buildbot server's master.cfg file contains FACTORY declarations which specify the commands that the WORKER will run on localhost.
@@ -337,9 +337,9 @@ Here are some highlights:
Best Practices:
-- When creating a new WORKER in the `master.cfg` file, leave a comment specifying the server and user account that this WORKER is called from. (At this time, taler.net is the only server used by this implementation, but it's still good practice.)
+- When creating a new WORKER in the ``master.cfg`` file, leave a comment specifying the server and user account that this WORKER is called from. (At this time, taler.net is the only server used by this implementation, but it's still good practice.)
-- Create a worker from a shell account with this command: `buildbot-worker create-worker <workername> localhost <username> <password>`
+- Create a worker from a shell account with this command: ``buildbot-worker create-worker <workername> localhost <username> <password>``
Then make sure there is a WORKER defined in master.cfg like: `worker.Worker("<username>", "<password>")``
