Environment Variables
Configure the public URL, secrets, the first admin, the database, and the security switches for your appliance. None of them is required: an empty .env boots.
How it works
Talon Studio is configured entirely through environment variables, read at container start. Set them in the .env beside the compose file, in Helm values, or in your platform's settings, then recreate the container (docker compose up -d) for a change to take effect.
Nothing is required. Every secret you leave unset is generated on first boot, kept in /data/secrets (mode 0600) and reused on every restart; a value you set always wins and is never written there. The ones you will usually set are NEXTAUTH_URL once a proxy is in front, and the first admin's username and email.
URL, secrets and first admin
The TALON_ADMIN_* variables apply only when the database has no users. They never change or reset an existing account.
Database and pySigma
Security switches
Logs, sessions and metrics
Content, AI and licence
There is no variable that changes the Community Edition limits, bypasses the licence check, or substitutes the key it verifies against. TALON_LICENSE_PUBLIC_KEY, SELF_HOSTED_COMMUNITY_MAX_* and SELF_HOSTED_TEAM_MAX_* are no longer read; remove them if an old .env carries them. The background loops and the AI assistant have further tuning variables, all with safe defaults.
An example .env
A .env for an install behind a TLS proxy: