adds information on modules, installing them and where testcloud is required
Details
Details
read docs, do they make sense?
Diff Detail
Diff Detail
- Repository
- rLTRN libtaskotron
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
| docs/source/index.rst | ||
|---|---|---|
| 78–79 | ``libtaskotron-core`` if you want to make it pretty :-) | |
| 109–111 | This seems clearer to me: The bits needed to enable execution with <disposable clients>. Without this module you can only use local execution or a persistent remote machine execution. This module depends on `testcloud <https://github.com/Rorosha/testcloud>`_ which will pull in several other non-trivial dependencies. The disposable clients part could be a hyperlink to a document where we give more details about them, if there's such. | |
Comment Actions
- adding disposable client docs, linking from index
- forgot to add diagram images for new page
Comment Actions
Great new docs, thanks a lot.
| docs/diagrams/disposableClientExecution.svg | ||
|---|---|---|
| 2–5 | Shiny! For the disposable image, could the arrows be sorted top-to-bottom in the same order as the steps are executed? I.e. arrow number 1 (step number 1) top most, arrow number 4 bottom most. It would be easier to read the image. | |
| docs/source/disposableclients.rst | ||
| 25–26 | I'd put Executor below Overlord and Minion, so that the description follows the usual workflow Overlord -> Minion -> Executor. | |
Comment Actions
- adding disposable client docs, linking from index
- forgot to add diagram images for new page
- changes labels and order of arrows in diagrams
- changing description order to match what disposable clients actually do
Shiny! For the disposable image, could the arrows be sorted top-to-bottom in the same order as the steps are executed? I.e. arrow number 1 (step number 1) top most, arrow number 4 bottom most. It would be easier to read the image.