Environment Variables
Lex App reads its runtime configuration from environment variables — usually loaded from the .env file lex setup generates at your project root. This page lists the variables the framework actively reads.
This index covers the variables the framework reads directly. Your project's Django settings may layer additional ones on top. If a variable isn't listed here, check
lex_app/settings.pyin the installed package.
Async / Celery
Variable | Purpose |
|---|---|
|
|
| Set to |
Streamlit
Variable | Purpose |
|---|---|
|
|
Keycloak / OIDC
Variable | Purpose |
|---|---|
| Name of the Keycloak realm the framework targets when syncing models, fields, and groups. |
| Display name of the realm (used during bootstrap). Falls back to |
| Your project's OIDC client ID — the identifier the browser logs in against. |
Additional KEYCLOAK_* / OIDC_* variables (server URL, client secret, admin credentials) are read at the Django-settings layer. lex setup writes a complete set into your .env — start from that file rather than constructing the list by hand.
Variable | Purpose |
|---|---|
| API key used to send the PDF test report ( |
Where these get set
Place | When it's used |
|---|---|
| Local development. Loaded by PyCharm run configs and |
Container / cloud env | Production. Whatever your platform's secret manager exposes (Docker |
If you change anything in
.env, restart yourlex start/lex streamlitprocesses (and your Celery workers if you have them) — the variables are read once at startup.
See also
- CLI Commands — every command that reads these variables.
- lex_config.py — the Python-side configuration that complements these env vars.
- Installation — how
.envis generated bylex setup.
Was this helpful?
Your feedback shapes what we write next.
