Optional services
Loomkeep runs without any of these. Each is the setup loomkeep.app itself
uses, packaged as a compose override: add its file to COMPOSE_FILE, fill in
its variables, and restart. Remove the file to turn it off.
| Service | What it adds | File |
|---|---|---|
| Monitoring | Grafana dashboards, searchable logs, metrics; job monitoring | docker-compose.observability.yml |
| Error tracking | GlitchTip, errors grouped and alerted | docker-compose.glitchtip.yml |
| Analytics | Umami, cookie-less stats for the public landing page | docker-compose.umami.yml |
| Feature flags | Unleash: maintenance per domain, a news banner | docker-compose.unleash.yml |
| Docker UI | Portainer, to manage containers from a browser | docker-compose.portainer.yml |
| Single sign-on & dashboard | Authelia for one login, Homepage as a start page | docker-compose.authelia.yml, docker-compose.homepage.yml |
Services with a web interface get their own subdomain behind Caddy
(grafana.<DOMAIN>, errors.<DOMAIN>…), so they need the
HTTPS override and DNS records for those names.
GlitchTip, Unleash and Umami keep their data in Loomkeep’s PostgreSQL, in
databases of their own: no extra database to run.