Configuration
How Prelude TE is configured — environment variables at startup, application settings at runtime.
Prelude TE has two configuration surfaces:
- Startup environment variables — port, TLS, storage path, timezone, logging. Set on the container (or systemd unit) and take effect on restart.
- Runtime settings — BGP identity (Router ID, Local AS, Passive mode), peers, outputs, users, tokens, licensing. Managed live through the web UI or the REST API.
For the full environment-variable reference, the production Compose example, the storage layout, and what changes through the UI vs. through env vars, see Deployment / Configuration reference.
The defaults are designed to make a fresh container come up with
HTTPS on port 4040, a self-signed certificate, and a writable
./storage directory — no env vars required for an evaluation
install.
Next
With the engine ready for your environment, move on to Licensing to confirm your tier — or skip straight to First peer if Community is enough for what you are evaluating.