v1.10.0: ntfy and Gotify notifications

Jellydash can now send playback and Jellyseerr request alerts to ntfy and Gotify. Both are optional and configured through .env, alongside Telegram, Discord, Pushover and Web Push.

Setup

For ntfy, set NTFY_URL to the server's base URL and NTFY_TOPIC to your topic. Add NTFY_TOKEN if the server requires an access token. Servers that allow publishing without authentication also work. Use a protected topic for private playback information.

For Gotify, set GOTIFY_URL to the server's base URL and GOTIFY_APP_TOKEN to an application token.

Subscribe to the topic in your ntfy client, or connect your Gotify client to your server. Set APP_URL to your Jellydash URL to include dashboard links in alerts. This URL needs to be reachable from your device.

The notification setup guide includes configuration examples for both providers. Existing notification channels keep working without any new settings.

If one provider is unavailable, Jellydash still tries the others. As with the existing channels, an alert counts as delivered once any channel succeeds. A failed channel does not get a separate retry after another succeeds.

Update

docker compose pull && docker compose up -d

If you use an older MariaDB Compose file, copy the new notification environment entries from the current docker-compose.yml into your Jellydash service, preserving your own settings. Adding the values to .env alone does not pass them into that container. The SQLite Compose setup already reads .env through env_file.

After changing notification settings, recreate the container so it receives them:

docker compose up -d --force-recreate app

Use your Jellydash service name if you renamed it in Compose. No manual database migration is needed for this release.