Roastwarden

Releases ·

Roastwarden 0.27.0

The server's public address can be set in Settings → Roasting, so share pages, label QR codes and approval links point where others can open them. After the rename, the last backup names its file again, and a share link that is no longer active says so plainly. Checked live: a server outside the LAN imported a shared profile from production over the internet.

Added

  • Public address in Settings → Roasting (public_url): where share pages, label QR codes and approval links point. It could only be set through the API before, and unset, a link made by roast on the server itself read http://localhost:8080. The field fills in the page's own address; INSTALL.md says when to set it.

Fixed

  • The last backup names its file again: after the rename (0.25.0) the backups were renamed roastwarden-<time>.db at start, but the record of the last run still named the old rustroast-<time>.db, so Settings → Backups and roast status showed a copy that no longer existed. Migration 059 renames the stored names the same way.
  • A share link that is not active has its own error code, LINK_NOT_ACTIVE (404), so roast profile import-link says to ask for a new link instead of "list what exists with roast roasts…".