> For the complete documentation index, see [llms.txt](https://docs.monitorss.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monitorss.xyz/configuration/environment-variables.md).

# Environment Variables

### Bot

All configs can be overridden with environment variables. Each variable must be prefixed with `DRSS`, and each depth is marked by an underscore `_`. All variables must also be capital. For example:

`config.database.uri`=`DRSS_DATABASE_URI`

`config.bot.token`=`DRSS_BOT_TOKEN`

For any configs that are arrays such as owner IDs, they are simply strings separated by commas. For example, `DRSS_BOT_OWNERIDS=123,456,789`.

### Web

The same rules apply, but instead of `DRSS` prefix, it's `DRSSWEB`. For example:

`config.database.uri`=`DRSSWEB_DATABASE_URI`

`config.bot.token`=`DRSSWEB_BOT_TOKEN`

A special env variable `DRSS_START` can be equal to `bot` to only start the bot,  `web` to only start the web, or `bot-web` to both bot and web with the `npm start` command.


---

# 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.monitorss.xyz/configuration/environment-variables.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.