Roastwarden

Releases ·

Roastwarden 0.26.0

Profiles can be shared: a public link shows a profile's curve, targets and events and offers it as a file, and another Roastwarden imports it from the link. The names from before the rename are gone from the wire (firmware must watch roastwarden/server/status, as the reference ESP32 firmware does from 3.7.0), and the owner's production moved to its new address.

Added

  • Shared profiles (Next 72, Profiles, "Sharing a profile"): a public link for a profile, /P/<code>, whose page shows its curve, targets and events and offers it as profile.json (Roastwarden) and profile.alog (Artisan); revocable, views and downloads counted. Import from a link reads another server's shared profile (public addresses only, the address pinned, no redirects) and makes a profile that says where it came from. Dashboard: a profile's page → Share, Profiles → Import from a link; agents: roast profile share | shares | unshare | import-link; eval task 55. Migration 058.

Changed

  • Production moved to its new address (the owner's instance; owner 2026-11-03: "fix things correctly and not by implementing a bunch of redirects"): the old name answers nothing. Browsers sign in and allow notifications again, the installed app is installed again, and labels printed before with a QR code to the old name open nothing.

Removed

  • The names from before the rename, on the wire (Next 72): the server no longer announces itself on rustroast/server/status (it clears that topic's retained message at start) or browses _rustroast._tcp, and both ACLs drop the old topic. Roaster firmware must watch roastwarden/server/status (the reference ESP32 firmware from 3.7.0). Old RUSTROAST_* variables and the database's old name are still read (Running it, "Upgrading from rustRoast").