> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/setup-docs/introduction/readme.md).

# Setup Documentation

View Xibo CMS recommended setup and configuration for cloud hosted and self hosted digital signage deployments.

Use these resources to setup, configure, and manage Xibo software.

The documentation covers the core tasks for Xibo digital signage deployments. Start here if you need Xibo CMS installation guidance, configuration help, or deployment options.

### Get Started

* Install a Xibo Cloud hosted CMS or self host
* Connect media players to your Xibo CMS
* Configure to suit your deployment

#### Choose your installation path

* [Xibo Cloud Hosted CMS](/setup-docs/cms-installation/cloud-hosted-cms.md)— use a managed Xibo CMS service
* [Self hosted CMS](/setup-docs/cms-installation/self-hosted-cms.md)— deploy Xibo CMS with Docker on your own infrastructure<br>

#### Install the Player App

* [Installing and Upgrading the Player App](/setup-docs/player-app-installation-and-upgrades/player-app-installation-and-version-upgrades.md)

<details>

<summary>How many media Players can I connect to Xibo?</summary>

Xibo itself doesn’t impose a hard limit on the number of media players that can connect to a single CMS.

We know of production instances of Xibo running many hundreds of media players against a single server. The limitations come from the hardware you choose to deploy your CMS on.

Asking what hardware is required is a little like asking how long the proverbial piece of string is. Everyone’s display workloads are very different depending on the frequency and content of the media updates made to the layouts the CMS is hosting, the frequency with which "Displays" connect to the CMS and how aggressively media items such as RSS feeds are set to be cached.

For most small to medium deployments, quite modest server hardware should be sufficient. For larger deployments, take the time to simulate some production workloads and then scale out from there to work out the resources you’ll need to service your media players.

</details>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/setup-docs/introduction/readme.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 `build a script that syncs our docs to a CMS` 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.