# Configuration

Runtime settings, site languages, themes and browser assets.

## Runtime environment

Keep credentials in `.env`, outside tracked application content. The framework repository includes `.env.example`; use it as the current settings reference rather than copying secrets between projects.

| Setting | Purpose |
|---|---|
| `APP_ENV` | Environment label |
| `PEPPER` | Stable secret used by authentication and encrypted data |
| `SITE_URL` | Public URL for jobs that generate absolute links |
| `BASE_PATH` | Optional prefix for an alias or subdirectory installation |
| `TRUSTED_PROXIES` | Explicit trusted proxy addresses, when behind a proxy |
| `JOB_RUN_DELAY_MS` | Delay between processed background jobs |
| `MAIL_SERVICE`, `MAIL_FROM`, `MAIL_FROM_NAME` | Mail delivery configuration and project sender identity |

Use `env()` in PHP for runtime settings. `[#env#]` excludes secrets that templates should not output. See [email](/en/docs/guides/email/) for service-specific mail settings.

## Site settings

The `.config/site` record describes the site name, description, languages, text direction and admin sidebar placement. The administration settings page edits these values for authorized users. Page metadata is distinct from site settings.

## Theme and assets

Application theme choices live in `ext/tailwind.theme.js` and `ext/theme.css`. Tailwind CSS scans template classes at build time: use discoverable complete class names. Run `./nimbly build` after changing build inputs. See [Build](/en/docs/operate/build/).