How to deploy Zulip with Docker Compose

• Compose: Getting started
  • Next steps
  • See also
• Compose: Providing settings via environment
  • Providing settings in compose.override.yaml
    • Example
  • Providing settings in a zulip-settings.env file
    • Example
  • See also
• Compose: Configuring TLS
  • Using a self-signed certificates
  • Using certbot to acquire Let’s Encrypt certificates
  • Manually configuring certificates
  • Deploying behind a reverse proxy
  • See also
• Compose: Remapping published ports
  • Why redeclaring ports in compose.override.yaml does not work
  • Replacing the ports list with !override
  • See also
• Compose: Secrets management
  • Store secrets in a .env file
  • Store secrets in files in a directory
  • Additional secrets
  • Rotating the PostgreSQL password
  • See also
• Compose: Providing settings using files
  • Manually control just the contents of settings.py
  • Store settings.py in the Docker volume
  • See also
• Compose: Configuring authentication methods
  • See also
• Compose: Incoming email
  • See also
• Compose: Outgoing proxies
  • See also
• Compose: Upgrading
  • Upgrading to a release
  • Upgrading from a Git repository
  • Troubleshooting
    • git checkout refuses with “local changes would be overwritten”
  • See also
• Compose: Upgrading from the legacy zulip/docker-zulip image
  • Plan and back up
  • What changed
    • Image
    • Configuration layout
    • Setting renames and removals
    • Volume layout
  • Migrate to the 12.x layout
  • Bring the new image up
  • See also
• Compose: Running commands
  • Running management commands
  • See also
• Compose: Using existing services
  • See also
• Building custom Zulip images for Docker Compose
  • Running custom scripts on startup
  • Rebuilding the Docker image
  • Per-file overrides
  • See also
• Compose: Backups
  • Take a backup
  • Get just the database dump off-box
  • Restore from a backup
  • Off-site database backups
  • See also