Topic
1 news article · 8 tutorials
SQLite on one free box is one disk failure away from gone. Here is the exact Litestream-to-R2 setup I run across every PocketBase backend in my stack, including the restore drill and the gotcha that bites first.
I upgraded PocketBase, my migration code threw a cascade of 400s and 404s, and one collection came back empty with a 200. The breaking change is the `schema` to `fields` rename plus flattened field options, and this is the full fix.
I run Coolify on a single free Oracle A1 box in Mumbai as the control plane for 15-20 production apps. This is the real install, the Git-push deploy flow, the Cloudflare Tunnel that keeps every port closed, and the API quirks nobody documents.
A non-traditional operator running real production sites on Claude Code, Coolify, PocketBase on Oracle ARM, and Cloudflare. The real workflow is Opus as orchestrator plus subagents executing, governed by hard gates: verify before claiming done, snapshot before destructive ops, and a flat refusal of --no-verify and --force. Here is what works, and the failure modes a non-engineer hits shipping to prod in India.
Oracle's ARM free tier gives you 4 OCPUs and 24GB RAM for zero rupees, and it genuinely runs real workloads. I host Coolify, several PocketBase backends, and a Cloudflare Tunnel on one A1 box. Here is what actually breaks, the capacity game nobody warns you about, and the Docker bridge gotcha that breaks tunnels silently.
PocketBase and Supabase both promise a backend in a weekend. One of them bills you per project; the other is a single binary you own forever. Here is why every backend in my multi-site setup runs PocketBase on Oracle ARM, the real migration off Supabase, and the breaking changes nobody warns you about.
PocketBase is the single-binary backend I use across my SaaS empire. Wired to Claude, it gives you auth, DB, files, and AI features in one Linux process. This is the install.
Supabase is the default Indian-startup BaaS choice. I run PocketBase instead across the empire. This piece explains why, with the cost math and migration trade-offs.
