Production Deployment Guide

Deploy Bellamy Book as a self-hosted social network (one instance = one community).

Canonical guides

This page is a short map. Prefer the detailed Self-Hosting docs for step-by-step install.

Recommended paths

Who	Path	Guide
Operators / customers (no source build)	Pre-built Docker images (dockerPublish)	Self-host with pre-built images
Test before DNS	Same kit, local override	Local testing
Production DNS + HTTPS	Traefik on the server	Traefik when you deploy
Full monorepo stack	dockerProd Compose (build from source)	Docker Compose (full project)
Architecture overview	What runs where	Deployment architecture

Start here: Self-Hosting intro.

Pre-deployment checklist

• Domain DNS for frontend, admin, API (and Traefik hosts)
• .env filled: secrets, JWT, DB passwords, MinIO (or R2), public URLs
• MongoDB keyfile created
• SSL/TLS via Traefik / Let’s Encrypt (or your proxy)
• SMTP / Turnstile / OAuth / LiveKit as needed
• Backup destination configured (Backups)
• Monitoring optional (Monitoring)
• License plan ready (License system)

After first boot

1. Open Admin URL → login as Admin
2. Activate license (CONSUMER) if required
3. Set application settings (registration, defaults)
4. Verify Frontend login, media upload, chat hubs
5. Schedule backups

Security & ops

• Security architecture
• Environment configuration
• Updates
• Troubleshooting

What not to do

• Do not invent a separate ad-hoc docker-compose.prod.yml when dockerPublish / dockerProd already exist
• Do not expose Postgres/Redis/Mongo/Kafka ports to the public internet
• On the server, do not use the local-testing Compose override (it disables Traefik)