Deployment

Overview

Production separates marketing, dashboard, API, documentation and status origins. Staging stays private and local development must never target production by default.

Setup & requirements

Operators use reviewed main commits, isolated MailRaft resources and protected server storage. Run tests, inspect pending migrations, back up existing data, deploy only affected MailRaft services, then verify public TLS, cookie boundaries and tenant isolation.

Usage & verification

Deploy a reviewed main commit after checks, database/RLS, API/MCP and browser tests. Recreate only affected MailRaft containers. Verify the API health endpoint and public headers, then compare deployed file hashes and the remote Git SHA. Do not run a shared-host Docker prune or restart the shared proxy.

Staging and local databases have separate identities. Never run reset or seed commands against production. Keep external campaign and messaging policies disabled throughout migrations and restore validation.