B&J — service uptime, memory footprint, and tunnel reachability (v2, verified 2026-05-24)
boucherjones-web.service snapshot
| Metric | Value |
|---|---|
| Active state | active (running) |
| Uptime since last restart | 2h 36min (since 2026-05-23 21:39:42 UTC — yesterday's audit-closure deploy) |
| Memory (current) | 63.0 MB |
| Memory (peak) | 68.0 MB |
| CPU time consumed | 668 ms total across 2h 36min |
| Tasks | 13 |
| Process | next-server (v16.2.6) |
| Deploy invocation | git pull && npm ci && npm run build && sudo systemctl restart boucherjones-web |
Journal summary (last 1,000 lines)
| Severity | Count |
|---|---|
| Lines containing "error" | 38 |
| Lines containing "warn" | 0 |
The 38 "error" lines are all the same incident: a short window on 2026-05-19 where the unit booted before npm ci had finished writing the next binary in node_modules, producing repeated Error: Cannot find module '/opt/boucherjones-web/node_modules/next/dist/bin/next' on restart-loop until the deploy completed. The unit has been healthy since. No application-level errors in the current window.
Cloudflare tunnel
| Check | Result |
|---|---|
cloudflared installed |
yes — version 2026.3.0 (built 2026-03-09) |
https://bjweb.candidcreative.ca/ reachable |
200 OK (initial response 5.2s — likely a cold revalidation; subsequent hits ~50–100 ms) |
https://bjweb.candidcreative.ca/agriculture reachable |
200 OK |
| Tunnel ingress | routes to 127.0.0.1:3201 per /etc/cloudflared/config.yml |
What this enables in case-study copy
"Production memory footprint sits at 63 MB; CPU is effectively idle between requests (668 ms total CPU over 2h 36m of uptime)."
"Self-hosted, Cloudflare-fronted, single LXC container — ~$10–20/month all-in. No subscription stack." (Cost number cross-referenced from B&J marketing site stack (
bj-next, dev URLbjweb.candidcreative.ca) — VERIFIED LIVE STACK.)