Deployment
Ways to run Bulwark on your own servers: static files, Docker and Compose, Stalwart's application install, Kubernetes or a manual install, and how to update each one.
Requirements and sizingWhat Bulwark and Bulwark Lite need to run, which architectures are built, and how much memory they used in a measured setup.Static hostingBuild inputs, config.json, the CORS setting on Stalwart, and host snippets for Bulwark Lite.Docker deploymentDeploy Bulwark with Docker and Docker Compose.Docker ComposeRun Bulwark alongside Stalwart with Docker Compose.Reverse proxySet up a reverse proxy in front of Bulwark.Run Bulwark at homeStalwart and Bulwark on a home server, NAS or ARM board: Compose, a reverse proxy, bind mounts, Lite on an existing web server, and packages other people maintain.Running several instancesRun Bulwark as several replicas behind one load balancer, with a shared Redis-protocol store.Install on StalwartLet Stalwart host Bulwark Lite itself as a web Application, on the same origin, with no web server and no CORS.KubernetesRun Bulwark on Kubernetes with the project's manifests (one or many replicas) or the community HelmForge chart.Manual deploymentDeploy Bulwark manually on a server.Running Bulwark for customersOne Bulwark for many customer domains: servers picked by domain, branding per web address, opening a mailbox from your panel, embedding, and several replicas.MonitoringSend errors to your own error tracker, scrape Prometheus metrics, wire up health checks and export OpenTelemetry traces.Security fixes and updatesWhere fixes are announced, how Bulwark tells you about a new release, and how to verify a download or image.UpdatingRelease channels, how to upgrade each install type, and how the update notice works.Upgrading to Stalwart 1.0What to do on the Bulwark side when a server moves to Stalwart 1.0, and which server settings to check.