Deploy

Overview

A shared Dory deployment usually starts with runtime, persistence, public URL, authentication, AI provider, database network, and secret-management decisions.

PageUse caseFocus
Self-HostingYou are planning a team deploymentArchitecture choices, persistence decisions, rollout checks, and operational boundaries.
DockerYou need concrete container commandsdocker run, .env, ports, volumes, Postgres mode, and upgrades.
Environment VariablesYou need the configuration referenceRequired secrets, application database, AI, auth, email, OAuth, and related variables.
AuthYou are deciding how users sign inEmail login, verification, OAuth, initial admin, provisioning, and offboarding.
  1. Read Self-Hosting to choose storage, network, HTTPS, auth, and rollout boundaries.
  2. Use Docker for the actual container start command.
  3. Fill in required values from Environment Variables.
  4. Configure login rules in Auth.
  5. Validate with a test database before adding production connections.

Launch Checklist

  • Public access uses HTTPS.
  • BETTER_AUTH_URL matches 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?

Cloud Databases

Connect managed cloud databases to Dory with TLS, IP allowlists, SSH tunnels, secrets, and team access boundaries.

Self-Hosting

Plan the runtime, storage, network, security, and rollout boundaries for a shared Dory deployment.

On this page

OverviewQuick LinksRecommended OrderLaunch Checklist