wkulhanek/bonob
1
0
Fork 0
mirror of https://github.com/wkulhanek/bonob.git synced 2025-12-21 17:33:29 +01:00
Code Issues 1 Packages Projects Releases Wiki Activity

Udpates to docs

Browse Source
This commit is contained in:
Wolfgang Kulhanek
2025-10-26 12:01:07 +01:00
parent 2403d6cdc6
commit 8e207fd483
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
UPDATES.adoc
View File

@@ -4,7 +4,7 @@ Run Bonob on your server.
== Updates made to original code == Updates made to original code
* Proper Token handling after login. Also handling of periodic token refresh. * Proper Token handling after login. Also handling of periodic token refresh. Something is still funky here after a day or two...
* Store Tokens in an SQLite database (in mounted `/config` directory). * Store Tokens in an SQLite database (in mounted `/config` directory).
* Added variable `BNB_TOKEN_CLEANUP_INTERVAL` with a default of `60` (minutes) to set how often expired tokens should be cleaned up out of the database. * Added variable `BNB_TOKEN_CLEANUP_INTERVAL` with a default of `60` (minutes) to set how often expired tokens should be cleaned up out of the database.
* Multi-account logins. Register one Bonob and log in with multiple Navidrome users for easy account switching in the Sonos app. * Multi-account logins. Register one Bonob and log in with multiple Navidrome users for easy account switching in the Sonos app.
@@ -27,6 +27,7 @@ Run Bonob on your server.
Bonob now needs a volume to store the token database. In the example below that directory is `/var/containers/bonob`. Adapt as needed. Bonob now needs a volume to store the token database. In the example below that directory is `/var/containers/bonob`. Adapt as needed.
Also the example below uses a `bonob` user on the system with ID `1210` and group `100`. The database directory should be owned by that user. Also the example below uses a `bonob` user on the system with ID `1210` and group `100`. The database directory should be owned by that user.
Also for `BNB_SUBSONIC_URL` you can use the internal or external URL. So instead of `https://music.mydomain.com` you could use `http://192.168.1.100:4533` if your Navidrome runs on a server with IP `192.168.1.100`.
.Example systemd file (`/usr/lib/systemd/system/bonob.service`) .Example systemd file (`/usr/lib/systemd/system/bonob.service`)
[source] [source]
---- ----

4
sonos_service/SONOS_SERVICE.adoc
View File

@@ -5,7 +5,7 @@
+ +
image::images/about.png[] image::images/about.png[]
* Navidrome running and available from the Internet. E.g. via https://music.mydomain.com * Navidrome running and available from the server that Bonob is running on. This can be a public URL like https://music.mydomain.com or just a local URL like http://192.168.1.100:4533.
* Bonob running and available from the Internet. E.g. via https://bonob.mydomain.com * Bonob running and available from the Internet. E.g. via https://bonob.mydomain.com
You can use any method to make these URLs available. Cloudflare Tunnels, Pangolin, reverse proxy, etc. You can use any method to make these URLs available. Cloudflare Tunnels, Pangolin, reverse proxy, etc.
@@ -21,7 +21,7 @@ You can use any method to make these URLs available. Cloudflare Tunnels, Pangoli
*** Service Name: Navidrome *** Service Name: Navidrome
*** Service Availability: Global *** Service Availability: Global
*** Checkbox checked *** Checkbox checked
*** Website/Social Media URLs: https://music.mydomain.com (Some URL - e.g. your Navidrome server) *** Website/Social Media URLs: https://music.mydomain.com (Some URL - e.g. your Navidrome server). This has to be a valid URL.
** Sonos Music API ** Sonos Music API
*** Integration ID: com.mydomain.music (your domain in reverse) *** Integration ID: com.mydomain.music (your domain in reverse)