How revoltchat/self-hosted works
This repository packages Stoat for self-hosting rather than implementing the chat application itself. The documented operator workflow is to prepare a server and domain, generate secrets and configuration, then start the full instance with Docker Compose. The README identifies the deployed backend, web front end, file server, and metadata/image proxy. Source excerpts were unavailable, so service wiring and routing details are limited to relationships stated in the README; the Compose and Caddy configuration contents are not inferred.
Main entry points: compose.yml Compose deployment · generate_config.sh Config generator
Components 11
Host and setup
- Server and domain
- Config generator
generate_config.sh - Instance secrets
generate_config.sh
Instance deployment
- Compose deployment
compose.yml - Stoat backend
compose.yml - Web front end
compose.yml - File server
compose.yml - Metadata and image proxy
compose.yml - Caddy routing
Caddyfile
Operations
- Database migrations
migrations
Other components
- Instance operator
Connections 8
- Instance operator → Server and domain: prepares
README.md - Instance operator → Config generator: runs for domain
README.md - Config generator → Instance secrets: generates
README.md - Instance operator → Compose deployment: starts instance
README.md - Compose deployment → Stoat backend: deploys
README.md - Compose deployment → Web front end: deploys
README.md - Compose deployment → File server: deploys
README.md - Compose deployment → Metadata and image proxy: deploys
README.md