rttf

rttf · recipe pack · version 1.2.0

Your own S3 and static sites, with zero open ports

Garage S3 and nginx on your k3s cluster, with every bucket and key described in one file in Git. Sites go public through Cloudflare Tunnel, so nothing is forwarded on your router.

  • Deployed from zero
  • x86_64 and arm64
  • Ready for AI coding agents
A browser at https://files.example.com showing a clean index page served from a Garage website bucket
1 filedescribes every bucket and key
0ports opened on your router
0 changeswhen the setup Job runs again
9/9checks passed in the test

The problem

A fresh Garage is an empty box. Everything after that is by hand.

Layout, buckets, website access, keys and permissions: all manual, none of it in Git. Rebuild the cluster and you rebuild your storage from memory, which is the worst place to keep a config. And to make a site public you forward a port or run an ingress controller.

The usual way

  • Buckets and keys created by hand
  • Credentials copied around
  • Nothing to rebuild from
  • Ports forwarded to make it public

This recipe

  • Buckets, websites and keys in one spec.json
  • Credential Secrets created for you
  • Rebuild is a Git push
  • Outbound-only tunnel: no open ports

What you get

S3, static sites and the way in, in one folder

Flux manifests, a setup Job, a few small tools and a runbook. Describe your buckets, push, and the cluster does the rest.

Garage, Flux-ready

A single-node S3 with website hosting, running from your Git repository.

Setup as code

One spec.json: buckets, which are websites, which keys can do what. A Job creates them and the credential Secrets.

Safe to re-run

The Job only adds. It never deletes a bucket or revokes a key; a second run changes nothing.

Zero open ports

cloudflared connects outbound only. No ingress controller, nothing to forward.

nginx for static sites

Single-page apps and redirects from a volume, plus a tool to copy a folder into it.

Small tools and alerts

Upload a file into a bucket, render an index page for public buckets, and four optional alerts.

Made for AI coding agents

Hand it to your agent. Cloudflare changes wait for your yes.

The 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

Deployed on an empty VM, following the README as written

On x86_64 and again on arm64. Every check below passed, and each run started from VM creation.

  • Layout, buckets and keys created from an empty Garage
  • A second run changed nothing (exactly what you want from a setup script)
  • A file uploaded with a generated key and served at its hostname
  • nginx served the volume
  • Served through a real Cloudflare Tunnel, created and deleted by the test
  • Same result on x86_64 and on arm64
Test output: nine checks marked ok, from bootstrap and idempotency to a page served through the Cloudflare tunnel, ending in VERIFY PASSED
The test run, word for word (test hostname redacted).
File tree of the download: START-HERE.md and recipes/garage-static-web with AGENTS.md, README.md, a bootstrap folder, Flux manifests and tools
Exactly what is in the zip.

Is it for you?

Small, honest storage for small clusters

Yes, if you want buckets and static sites on your own k3s cluster, described in Git and reachable from the internet without port forwarding.

No, if you want more than three nodes or several sites set up for you. Garage can do both (more nodes, zones per site), but this recipe is built and tested for one node, or three with a copy on each (new in 1.2).

What you need

  • k3s v1.35 or newer, with the local-path storage class
  • Flux v2.10 or newer, kubectl, Python 3
  • For public access: a domain on Cloudflare and a tunnel token
  • x86_64 or arm64 (64-bit)

Pinned versions

  • k3s v1.37.2 · Flux v2.10.0
  • Garage v2.5.0
  • nginx 1.30.6
  • cloudflared 2026.10.7

Questions

Before you buy

Do I need Cloudflare?

Only for public access. Garage, the buckets, keys and nginx all work without it, and most of the README's checks need no Cloudflare. For public sites you need a domain on Cloudflare; the free plan is enough.

Can I add buckets and keys later?

Yes. Edit spec.json, render the manifest again, and push. The Job adds what is new.

Will a re-run ever delete something?

No. The setup Job only adds: it never deletes a bucket or revokes a key. The test ran it twice; the second run changed nothing.

Is my data replicated?

With three nodes, yes: the optional three-node setup keeps three copies, one per node, and any one node can go without S3 going down (new in 1.2, measured in the README). The default is one node with one copy. Either way, copies are not backups: pair it with the backups recipe, which mirrors your buckets every night and tests the restore every week.

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.

Storage you can rebuild with a Git push.

Describe your buckets once, keep them in Git, publish sites without opening a port. Tested from zero on x86_64 and arm64.

Get the recipe €19