Find music and request it from Lidarr or nexcrate. Accounts, single sign-on, quotas, API tokens.
1.5K
Find music and request it from Lidarr or nexcrate with one click.

nexbeat is a small, self-hosted companion to Lidarr, built in the spirit of Nexview: accounts with invitations, per-user quotas counted by request, optional approval, and a discovery page that recommends artists based on what the library and each user already have.
Status: stable. Used daily against Lidarr and nexcrate.
The screenshots show a throwaway instance with a few well-known artists as its library.
nexbeat never changes Lidarr settings. It adds and monitors artists and albums and starts searches, nothing else.
Two modes. The administrator picks where requests go. In ARR mode it is
Lidarr, as described above. In NEX mode it is nexcrate, through its
interface for other programs (/api/v1, contract 1 with music): nexbeat asks
for albums and whole artists (in the chosen album types), reads their state in batches
and listens to nexcrate's event stream, so a change shows up within seconds.
Connecting takes one step: nexbeat asks for a key, nexcrate shows a code, the
owner confirms it there. A key made by hand works too. nexbeat changes nothing
in nexcrate's settings either. Switching modes hands open requests to the new
program once.

mkdir nexbeat && cd nexbeat
curl -O https://raw.githubusercontent.com/DerKezorm/nexbeat/main/docker-compose.yml
docker compose up -d
Open http://<your-host>:8030 and create the first account. It becomes the
administrator. Then, under Settings:
In ARR mode the tab also shows a webhook address. Entered in Lidarr, it lets nexbeat notice finished downloads right away; without it, nexbeat checks every two minutes.
docker compose pull && docker compose up -dsecret.key
together. Without the key, the stored credentials cannot be read.latest follows releases, main
the current development state.
cd backend
python -m venv .venv
.venv/Scripts/python.exe -m pip install -r requirements-dev.txt
.venv/Scripts/python.exe -m uvicorn app.main:app --port 8030
cd frontend
npm install
npm run dev
Open http://localhost:5182 and create the first account.
Every account can create API tokens under Profile > API tokens. A token carries exactly the rights of its account; ticked as read only it may look things up and change nothing. The token is shown once, when it is created, and is sent with every request as a header:
Authorization: Bearer nxb_…
The promised interface is under /api/v1 and described at /api/docs:
GET /api/v1/me: the account behind the token and what it may do (may:
request, see_all, decide). Build buttons on may, not on the role.GET /api/v1/dashboard: requests by state and the size of the library in one
call. Administrators get the whole installation, everybody else their own
requests.nexdeck uses it for its nexbeat cards. Administrators see every token of the installation under Settings > Users. Changing the password leaves tokens working; deactivating an account stops them.
An app without a browser, such as the iPhone app nextune, does not need a token typed in. It asks for a code and shows it; you enter the code under Profile > API tokens > Connect a device with a code, and the app fetches a token of your account by itself. It then shows up in the list like any other token and can be revoked there.
POST /api/pairing/request (no sign-in): id, secret, code to show,
expires_at (ten minutes), poll_seconds.GET /api/pairing/request/{id} with the header X-Pairing-Secret:
waiting, or once confirmed with token and account. An expired or used
code answers 410.DELETE /api/pairing/request/{id} with the same header lets the code go.The code alone gives nothing away: only the app holds the secret, confirming needs a signed-in browser, and wrong codes are slowed down per account.
Under Settings > System > Sign-in an administrator finds three cards:
<public address>/api/oidc/<short name>/callback; the form shows it with a
copy button. Providers set up in nexbeat 1.3.0 keep the address they know,
/api/auth/oidc/<short name>/callback.Microsoft Entra ID: register a web app, enter the redirect address (Entra
only accepts https, except for localhost) and create a client secret. Issuer:
https://login.microsoftonline.com/<tenant ID>/v2.0, or common and
organizations for several tenants. Entra sends an email address only as the
optional claim email; nexbeat works without it.
Accounts are matched by the provider's subject only, never by email address. An existing account links itself under Profile > Sign-in providers, with its password once more. New people come in through an invitation (the invitation page has a button per provider) or, per provider, through "New people get an account"; such accounts start as members without a password and can set one in their profile.
Behind a reverse proxy that ends TLS nexbeat takes the scheme
(X-Forwarded-Proto) only from the addresses in FORWARDED_ALLOW_IPS (the
setting for trusted proxies: addresses or networks such as 172.16.0.0/12,
comma separated, * for all). It is empty by default, so nexbeat trusts no
sender until you name your proxy. It reads the rightmost value, the one your
proxy wrote. Setting the public
address is enough for sign-in itself; trusting the proxy also keeps the session
cookie Secure and silences the warning in the authentik card.
MusicBrainz, Cover Art Archive and ListenBrainz (open data). Artist images and 30 second previews can come from Deezer's web API. That source is off by default: it answers without a key, but Deezer no longer hands out keys to developers, so whether nexbeat asks it is up to you (Settings › Sources).
Once a day nexbeat asks GitHub for its newest release to tell administrators about updates. Nothing but the request itself goes out, and it can be switched off on the About page.
Content type
Image
Digest
sha256:74e5b09c8…
Size
73.7 MB
Last updated
about 22 hours ago
docker pull derkezorm/nexbeat