- runtime env vars (URLs, deployment mode, non-sensitive settings)
- secrets (credentials and keys)
- admin-managed platform settings (global configuration in the Noxus admin portal)
Configuration Sources
Environment Variable Layers
| Layer | Example |
|---|---|
| Base platform env | deployment env, URLs, storage mode, feature toggles |
| Service-specific env | frontend-only host binding, worker subscribe mode |
| Secrets | DB/Redis credentials, auth keys, provider secrets |
Deployment-Independent Principles
- Keep non-sensitive settings in environment config
- Keep credentials in secrets only
- Keep environment names simple (
local,staging,prod) - Do not expose internal-only controls (such as billing internals) in user-facing docs
Noxus supports extensive runtime configuration from the admin portal when the user has global admin permissions. This includes global server settings and auth behavior.
Practical Mapping In Your Stack
- VM compose:
env_fileand explicit env mounts - Helm:
env,extraEnv,secrets, plus service-specific secret variants - Terraform stage3: secret/env materialization and namespace-scoped injection