Feature request: edit server bookmarks (frequency, name, mode, bandwidth) in the admin GUI

[Gesiima]

Summary

Server-side bookmarks can currently be created and deleted in the admin GUI, but there is no way to edit an existing bookmark. In particular, the frequency and the bandwidth (bandwidth_low / bandwidth_high) cannot be changed from any GUI (web or app). The only way I found is to stop the service and edit /var/lib/vibeserver/bookmarks-<serial>.json by hand.

Use case

I run VibeServer on a Raspberry Pi with an RTL-SDR and a list of about 25 server bookmarks (bookmarks-<serial>.json). Over time, frequencies and filter widths need small corrections, for example a changed frequency or a different passband for individual stations. Today that means:

1. sudo systemctl stop vibeserver
2. edit the JSON in a text editor
3. sudo systemctl start vibeserver

This is error-prone (JSON typos), requires shell access, and the running server may overwrite the file in the meantime (e.g. lastHeard updates or learned RDS bookmarks).

Current behaviour

• Server bookmarks are stored per radio (bookmarks-<serial>.json) as objects with frequency, name, mode, bandwidth_low, bandwidth_high, manual, source and lastHeard.
• In the admin GUI I can only create and delete bookmarks; there is no way to edit an existing one.
• Changing the frequency therefore means delete + re-create, and changing the bandwidth is not possible from the GUI at all.
• It is unclear to me whether POST /bookmarks accepts bandwidth_low / bandwidth_high, and whether posting an existing frequency overwrites the entry or creates a duplicate.

Proposed behaviour

In admin mode, add an Edit action per server bookmark that allows changing:

• name
• frequency
• mode
• bandwidth_low / bandwidth_high

Optionally:

• an update endpoint (e.g. PUT/PATCH /bookmarks) using the same admin authentication (vs_admin_nonce / vs_admin_auth) as the existing write calls
• a simple bookmark manager per radio (edit, delete, reorder)
• validation on save, so a broken entry cannot be written

Alternatives considered

• Editing the JSON file manually (current workaround, see above).
• Delete and re-create via the GUI (works for the frequency, but not for the bandwidth).

Environment

• VibeServer: V12 beta
• Hardware / OS: Raspberry Pi, Debian-based
• Radio: RTL-SDR, mode: <shared / single user>
• Client: <web client / VibeSDR app + version>

Thanks for the great project! 📻

[Stuey3D]

Done, can't believe I overlooked that.