---
title: "Configuration | Booster docs"
description: "The environment variables Booster reads, and where it gets the policy."
url: https://booster.apps.wayne.edu/docs/reference/configuration.html
llms: https://booster.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# Configuration[#](https://booster.apps.wayne.edu/docs/reference/configuration.html#configuration)

This page lists the environment variables Booster reads; the table is generated by the docs build.

| Variable | Meaning | Default | Read in |
| --- | --- | --- | --- |
| BOOSTER_BOT_TOKEN | Push token for the hop data robot (bin/hop-data-bot.php). Never in git, never logged, never printed | none | src/Refresh/HopDataBot.php |
| BOOSTER_POLICY | Path to CREED's policy.json | none (uses the snapshot bundled with BOOSTER) | bin/refresh-hop-data.php |

Booster reads the policy straight from the `waynestate/creed` package in its own `vendor/`, so there is no copy to drift: `composer update waynestate/creed` is the whole refresh. `--policy` and `BOOSTER_POLICY` still override it for one run.

`.env.example` holds the placeholder. Booster reads no secrets, makes no network calls of its own and talks to no Citadel host. Everything it prints from an app (file names, diffs) has control characters stripped.

When Rector runs, Booster passes it a few `BOOSTER_*` variables of its own (the app path, the sets, the PHP target). They are internal; do not set them.