> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/installation-and-troubleshooting/operations.md).

# Running Trulyp on-premises

Once Trulyp is installed on your own server, you are in charge of keeping it healthy and up to date. These pages are your reference for that:

* [Configuration file](/trulyp/installation-and-troubleshooting/operations/configuration-reference.md): what's in `trulyp.toml` and when to edit it.
* [Command line](/trulyp/installation-and-troubleshooting/operations/command-line-reference.md): start, stop and inspect Trulyp from a terminal.
* [Logs and diagnostics](/trulyp/installation-and-troubleshooting/operations/logs-and-diagnostics.md): where to find the logs and how to collect them for support.
* [Health checks](/trulyp/installation-and-troubleshooting/operations/health-checks.md): monitoring Trulyp and using it behind a load balancer.
* [Upgrade, back up and restore](/trulyp/installation-and-troubleshooting/operations/upgrading-backup-and-restore.md): moving to a new version safely.
* [Uninstall](/trulyp/installation-and-troubleshooting/operations/uninstalling.md): removing Trulyp from a server.

Using SaaS or a trial? Then we take care of all of this for you.


---

# 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.infotopics.com/trulyp/installation-and-troubleshooting/operations.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.