diff options
| author | buckE <buckE@disroot.org> | 2020-06-23 05:55:25 +0000 |
|---|---|---|
| committer | buckE <buckE@disroot.org> | 2020-06-23 05:55:25 +0000 |
| commit | 7a937ebaf0966e6940d586021a4a28686b004281 (patch) | |
| tree | a7926c3182354e34f542167db33b26d0c785b7a6 /developers-manual.rst | |
| parent | dc84dc2fdbee220db6a160267bd563a517fdf550 (diff) | |
| download | docs-7a937ebaf0966e6940d586021a4a28686b004281.tar.gz docs-7a937ebaf0966e6940d586021a4a28686b004281.tar.bz2 docs-7a937ebaf0966e6940d586021a4a28686b004281.zip | |
more added `s
Diffstat (limited to 'developers-manual.rst')
| -rw-r--r-- | developers-manual.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/developers-manual.rst b/developers-manual.rst index 0d2ae1c1..85bf257f 100644 --- 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>")`` |