Backend docs login required

Operational reference for whoever administers the bike box fleet — what runs on a box, how to reach one, and how to deploy changes to it. This section is gated by Cloudflare Access; if you can read this, you're already authenticated.

No real credentials live on this page or anywhere in this site — not SSH passwords, not API tokens, not signing keys. This is a static site; treat anything published here (even login-gated) as something that could eventually leak. Ask whoever manages the fleet for actual secrets through a proper channel (password manager, direct message), not by adding them here.

Services reference Every systemd service on a box, what it does, and how to check/restart it. Access & deployment Reaching a box over SSH, the deploy script, and what needs restarting after a code change.

Fleet at a glance

4 boxes, numbered 1–4 (box_number in each box's config.toml), each broadcasting its own bikebox_hotspot_<N> WiFi network.
Each box has an onboard camera + LiDAR (Livox Mid-360) + IMU, orchestrated by crodie (the Pi-side Python app).
Storage is an NVMe drive mounted at /mnt/storage — that's what File Browser and the upload pipeline both operate on.