Small API, Node 22, running under compose on a 2 GB Hetzner box next to postgres and caddy. Under any real traffic the api container dies: says . I set in compose specifically to protect postgres. RSS sits around 300 MB…
Two months into the first thing I've had actually online. I ssh into a $5 box, , , and it works. Every tutorial past this point is CI pipelines, blue green, staging environments, terraform. Is what I'm doing an…
Currently postgres 17 in compose next to the app, data on a mounted volume, to R2 nightly from a cron container. 8 GB and growing maybe 400 MB a month. Two person team, no ops person, we ship a lot. Someone on the team…
Single VPS, docker compose, caddy in front. Deploy is . Compose stops the old api container, starts the new one, and for roughly 30 45 seconds caddy returns 502 while the new one boots. It's an internal tool so nobody…
says 1.42 GB for a fairly ordinary Express + Prisma API. I build locally and push to a private registry over home internet, so every deploy is a coffee break. Dockerfile is basically: I know this is bad. I don't know…
Side project, 30 req/s at peak, mostly reads, one postgres, one node api, one worker, plus about 40 GB of user uploads sitting in R2. A CX22 is around 4.50 euro a month and I'd run everything on it with compose. Fly…