← Graph

Kamal with Postgres backups, replicas and self-hosted monitoring

question 5 connections

Audience question combining three threads: (a) with Kamal and Postgres, can you get automatic backups, restoration, and maybe replicas? (b) Is there a recommended self-hosted logs stack now that Once/Teabags covers other pieces? (c) Any host-monitoring recommendation beyond the do-agent? Strzibny: Kamal treats databases and logs as opaque accessories, so it doesn't know or help specifically — backups for Postgres are done by running a small Docker container that dumps to an object store (similar pattern to Litestream); replicas require you to already know how to configure Postgres replication and translate it to Kamal. For self-hosted metrics/logs: Grafana + Prometheus (what 37signals uses) works but is DevOps in itself; Strzibny covers deploying that stack in his Kamal course. For simplicity, he recommends services like Better Stack. He has considered building a Kamal-aware wrapper that would unify database/logs/monitoring but hasn't done so.

answer_summary
Kamal doesn't help specifically with Postgres — run backup containers as accessories; replicas possible if you already know the topology. For self-hosted logs/monitoring, Grafana+Prometheus works (see his Kamal course) but is real DevOps; otherwise use a service like Better Stack.
question Kamal with Postgres backups, replicas and self-hosted monitoring
about
Grafana tool
Mentioned as part of the self-hosted stack (with Prometheus).
question Kamal with Postgres backups, replicas and self-hosted monitoring
about
Prometheus tool
Mentioned as part of the self-hosted stack (with Grafana).
question Kamal with Postgres backups, replicas and self-hosted monitoring
about
37signals company
Cited as running a self-hosted Grafana/Prometheus stack.
question Kamal with Postgres backups, replicas and self-hosted monitoring
about
Teabags tool
Referenced as an existing self-hosted solution from the Once ecosystem.
question Kamal with Postgres backups, replicas and self-hosted monitoring
asked_at
Q&A after the talk.

Provenance