Infrastructure
How much one small server carries
A load test of signed-in users doing what the app does all day, the first capacity numbers, and why production numbers from India say more about distance than about the server.
2 min
Infrastructure
Hosting, deployment, monitoring, and the decisions behind where things run.
11 posts.
InfrastructureA 308 that sent every link home
Reloading any page in the app, or opening a shared link, landed on Today. The SPA rewrite rules pointed at /index.html, and Cloudflare Pages redirects that to /. It had been true for every deployment.
1 min
InfrastructureWhat the free tier actually buys, checked against the account
The API runs on a GCP e2-micro because that's what Always Free covers - one instance, 30 GB of standard disk, an ephemeral IP. It turns out to be sitting exactly at that ceiling, which explains more of the outage two posts back than any single bug did.
3 min
InfrastructureOne outage, four root causes
The API went down behind a Cloudflare Tunnel error and stayed down through a reboot, an interrupted OS upgrade, a stale connection pool, and a box too small for its own workload. None of the four were the same bug.
9 min
InfrastructureA status page that watches the whole stack, finally
app and api had no DNS records for most of their existence, so there was nothing to monitor - which meant status.pacestreak.com kept quietly not telling the whole story even after both went live. Fixed, plus a lesson in why a 200 from the app proves nothing about the API behind it.
2 min
InfrastructureTwo repositories that are public on purpose
Everything in the PaceStreak org is private except the status page and the org's .github repo. Here is why neither should be 'fixed'.
1 min
InfrastructureWhere PaceStreak is now, and what stands between it and launch
A status report: what is built across the API, the app and the sites, what's tested, and the one unresolved decision (where the API runs) that everything else is waiting on.
2 min
InfrastructureWhy app and api have no DNS records yet
A proxied DNS record with nothing behind it returns 522, which looks like a broken product. So records wait for deployments.
1 min
InfrastructureEvery choice in the stack, and why
The complete technology list behind PaceStreak — domain, sites, monitoring, backend, tooling — with the reasoning, the rejected alternatives, and the constraints each choice created for the next one.
15 min
InfrastructureFour things that only break inside a container
Setting up the PaceStreak backend on uv, Ruff and ty, then wrapping it in Docker. Every real bug came from running it, not from reading it.
5 min
InfrastructureSetting up PaceStreak in public
Domains, monitoring, a status page and a landing site — and the four things that silently broke while doing it.
3 min