← Back to Documentation
Deploy & Configure
Configuration Guide
Configure environment variables, licensing, providers, and operational defaults.
Key Steps
- Start with license and portal variables, then configure auth, providers, sync, and logging.
- Keep secrets outside source control and rotate them through your normal credential process.
- Use staged environments to validate changes before production rollout.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Visual Reference
Configuration order
- Set deployment mode, portal URL, deployment secret, signing key, and self-hosted organization ID.
- Configure auth and session settings.
- Add provider credentials and model aliases only after licensing is healthy.
Secret handling
- Store deployment secrets and provider keys in a secret manager or equivalent protected store.
- Use separate credentials for development, staging, and production.
- Rotate any secret that appears in logs, screenshots, tickets, or source control.
Change management
- Record configuration changes in your deployment runbook.
- Restart services in a controlled window when changing auth, licensing, or provider settings.
- Review health checks and usage reports after each change.