> 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

Overview of how runner configurations are deployed, the core deployment parameters, and the runtime commands available after rollout.

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.