rttf

rttf · 3 recipes · monitoring 1.0.0 · S3 1.2.0 · backups 1.2.0

Monitor it. Host on it. Back it up.

The three things a small k3s cluster needs after "it runs": knowing what it's doing, somewhere to put files and sites, and backups that have actually come back at least once. Three tested Flux recipes, one price.

  • Deployed from zero
  • x86_64 and arm64
  • Ready for AI coding agents
The three recipes side by side: a Grafana Golden Signals dashboard, a static page served from a Garage bucket, and recovery drill output ending in VERIFY PASSED
3Flux recipes in one purchase
€13less than buying them one by one
2 archseach tested on x86_64 and arm64
3AGENTS.md procedures for your agent

What is in it

Three recipes that fit together

The S3 recipe creates the bucket the backups recipe needs, and the monitoring recipe adds dashboards and alerts for both. Each comes as its own zip with a README runbook, pinned versions and an AGENTS.md.

Grafana Golden Signals dashboard with sites up, request rate and latency panels

Monitor it

Monitoring in 1.5 GiB of RAM

  • Prometheus, Grafana, Loki and probes
  • A Golden Signals dashboard
  • Seven alerts, delivered by email

Full details →

A browser showing a clean index page served from a Garage website bucket

Host on it

Your own S3 and static sites

  • Garage S3 with buckets and keys in one file
  • nginx for static sites
  • Public through Cloudflare Tunnel, zero open ports

Full details →

Recovery drill output: a dropped database, a deleted file and two Postgres recoveries, all ok

Back it up

Backups you have actually restored

  • Nightly MariaDB and S3 backups
  • Postgres to any minute
  • Weekly restore tests that alert you

Full details →

Made for AI coding agents

Hand the folder to your agent. It asks before it changes anything.

Each recipe ships with an AGENTS.md and a CLAUDE.md written as an operating procedure: what to ask you, what to check first, the exact steps, how to verify, and where to stop for your approval.

Illustration of the steps in AGENTS.md, not a recorded session.

Tested, not promised

How the three were tested

  • Each recipe deployed on an empty VM, following its README as written
  • Monitoring with S3, and S3 with backups, tested together in one cluster
  • Each recipe tested on x86_64 and again on arm64

All three at once in a single cluster was not tested; it needs a bigger machine than the one used.

Questions

Before you buy

Do I get three separate downloads?

Yes. Each recipe is its own zip with a START-HERE.md, a README runbook, a VERSIONS.md and the agent files, so you can set them up one at a time.

In which order should I set them up?

S3 first, because it provides the bucket the backups recipe uses for Postgres. Then backups, then monitoring, which adds dashboards and alerts for the other two.

Is it highly available?

Partly. The S3 recipe can run on three nodes, with a copy on each, so any one node can go. Monitoring and backups run as single copies; an HA monitoring recipe is on the bench.

Does it run on a Raspberry Pi?

It runs on 64-bit ARM: it was tested from zero on an arm64 VM. It was not tested on a Pi itself, and 32-bit ARM is not supported.

Everything after "it runs", in one purchase.

Monitoring, storage and tested backups for a small k3s cluster, all in Git. Each recipe tested from zero on x86_64 and arm64.

Get all three €59