Overview
A shared Dory deployment usually starts with runtime, persistence, public URL, authentication, AI provider, database network, and secret-management decisions.
Quick Links
| Page | Use case | Focus |
|---|---|---|
| Self-Hosting | You are planning a team deployment | Architecture choices, persistence decisions, rollout checks, and operational boundaries. |
| Docker | You need concrete container commands | docker run, .env, ports, volumes, Postgres mode, and upgrades. |
| Environment Variables | You need the configuration reference | Required secrets, application database, AI, auth, email, OAuth, and related variables. |
| Auth | You are deciding how users sign in | Email login, verification, OAuth, initial admin, provisioning, and offboarding. |
Recommended Order
- Read Self-Hosting to choose storage, network, HTTPS, auth, and rollout boundaries.
- Use Docker for the actual container start command.
- Fill in required values from Environment Variables.
- Configure login rules in Auth.
- Validate with a test database before adding production connections.
Launch Checklist
- Public access uses HTTPS.
BETTER_AUTH_URLmatches the URL users open.- Application data is persisted through a volume or Postgres.
- Initial admin, login method, and offboarding process are decided.
- Production database connections use readonly credentials first.
How is this guide?