> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/microservices/service-runners/deploying-runners.md).

# Deploying Runners

Runner configurations do not mandate deployment of these capabilities on a specific platform. It is possible to define any number and type of new runners using different programming languages or frameworks. Runners shipped with Rierino for different use cases are listed in this section.

Typical deployment requires only 3 parameters in a properties file or via [Deployments](/devops/microservices/deployment-packages.md) screen:

| Parameter                                  | Definition                                                                           | Example                                   |
| ------------------------------------------ | ------------------------------------------------------------------------------------ | ----------------------------------------- |
| rierino.runner.\[runner].class             | Fully qualified class name for the runner                                            | com.rierino.runner.spring.CRUDEventRunner |
| rierino.runner.\[runner].element           | Id of the runner configuration                                                       | crud-0001                                 |
| rierino.runner.\[runner].deploymentVersion | Version of the runner deployment (allows multiple versions running at the same time) | 1                                         |

Once designed and deployed, it is possible to send certain commands to a runner's instances through the user interface menu (for more commands, [Command Center](/devops/administration/sending-commands.md) can be used):

* **Ping:** Sends a ping command to all deployments and partitions of a runner and waits for 5 seconds to check if all the runners are healthy.
* **Rebuild:** Sends are build command to update all runner deployments in real-time, which can be used after operational elements of a runner are edited.
* **Deployments:** Lists deployments including the runner.
* **Dependents:** Lists other runners which use a specific runner as a base.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rierino.com/devops/microservices/service-runners/deploying-runners.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.