# \_index

Orbit Server can be run right out of the box, with several easy ways to get started.

## Docker container

The simplest way to start an Orbit Server for development is in a Docker container from the Docker Hub [image](https://hub.docker.com/r/orbitframework/orbit).

\`\`\`shell script

> docker run -it -p 50056:50056 orbitframework/orbit: \`\`\`

## Kubernetes

Orbit Server comes packaged as a helm chart hosted on Github. Include Orbit Server as a dependency in your application's helm charts.

```yaml
dependencies:
- name: orbit
  version: {{< release >}}
  repository: https://www.orbit.cloud/orbit
  condition: enabled
```

To configure Orbit, set overrides in a values.yaml file or use the --setValues switches when running `helm install`.

```yaml
orbit:
  url: localhost
  node:
    replicas: 1
    containerPort: 50056
  addressableDirectory:
    replicas: 1
  nodeDirectory:
    replicas: 1
```

## Hosted

Most scenarios are supported with the turnkey methods above. For some advanced situations, it may be preferred to host the Orbit Server runtime within an existing server application.

For help on hosting Orbit Server, check out the [Hosting](https://github.com/orbit/orbit/tree/03de01d5a629c8606cd109b85a8a3714491d7c67/server/hosting/README.md) page.

The best example of hosting the Orbit Server components can be found in the [**orbit-application**](https://github.com/orbit/orbit/blob/master/src/orbit-application/src/main/kotlin/orbit/application/App.kt) module.


---

# Agent Instructions: 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:

```
GET https://docs.orbit.cloud/docs/content/server/_index.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.