doc: markup kapow as program role

Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>
This commit is contained in:
pancho horrillo
2019-12-11 12:41:18 +01:00
parent 1cb328646e
commit 171f8c0410
2 changed files with 4 additions and 4 deletions
+3 -3
View File
@@ -14,14 +14,14 @@ The user makes a request to the `User HTTP Interface`.
- The request is matched against the route table. - The request is matched against the route table.
- ``kapow`` provides a `HANDLER_ID` to identify this request and don't mix it - :program:`kapow` provides a `HANDLER_ID` to identify this request and don't mix it
with other requests that could be running concurrently. with other requests that could be running concurrently.
2. spawn 2. spawn
-------- --------
``kapow`` spawns the executable specified as entrypoint in the matching :program:`kapow` spawns the executable specified as entrypoint in the matching
route. route.
The default entrypoint is ``/bin/sh``; let's focus on this workflow. The default entrypoint is ``/bin/sh``; let's focus on this workflow.
@@ -58,7 +58,7 @@ The shell dies. Long live the shell!
5. response 5. response
----------- -----------
``kapow`` finalizes the original request. Enjoy your banana now. :program:`kapow` finalizes the original request. Enjoy your banana now.
.. todo:: .. todo::
+1 -1
View File
@@ -139,7 +139,7 @@ Explanation:
Launch the Service Launch the Service
++++++++++++++++++ ++++++++++++++++++
At this point we only need to launch ``kapow`` with our ``ping.pow``: At this point we only need to launch :program:`kapow` with our ``ping.pow``:
.. code-block:: console .. code-block:: console