nzbfast: add app - #5992
Open
nzbfast wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nzbfast 1.1.2
nzbfast is a speed-focused Usenet (NZB) downloader written in Rust: one small binary, low memory footprint, and it saturates a fast line with a handful of connections. Articles are verified as they arrive, so most jobs finish with no separate verify pass, and repair and unpack run only when they are needed.
nzbfast/nzbfast:1.1.2@sha256:f427069f3ef33b9e7837ed84f8b7429d3d762099c9404e92d1216303c9f7a6ba- the project's own image, published to Docker Hub and ghcr from the same build,linux/amd64+linux/arm64, publicly pullable.Packaging notes
ports:.PROXY_AUTH_WHITELIST: "/api*,/newznab/api*,/jsonrpc*"- these are the SABnzbd-compatible API, the Newznab search endpoint and the NZBGet JSON-RPC facade. Sonarr/Radarr/Prowlarr and the mobile remotes talk to those and cannot present an Umbrel session cookie, so they authenticate with nzbfast's own API key instead. The container generates a key on first run and refuses to start keyless on a published port, so the whitelisted paths are never unauthenticated. This mirrors what the SABnzbd package does with/api*./configis the install - settings, the API key, the queue, history and the index database - so it is a bind mount under${APP_DATA_DIR}/data, together with the watch folder. Both source directories are committed with.gitkeep.STORAGE_DOWNLOADSinpermissions:.user:is not forced.Default credentials
None. There is no login; the app opens straight to the dashboard behind Umbrel auth. The API key that Sonarr/Radarr need is generated per install and shown under Settings → Security, so
defaultUsername/defaultPasswordare empty rather than fabricated.Testing
npm run lint:apps -- nzbfast --check-imagesreports no issues, andgit diff --checkis clean.I do not have an umbrelOS device, so the install has not been exercised through Umbrel itself. What has been verified is the container this package runs, deployed from the same compose shape on Linux: it reaches its healthcheck, the dashboard serves,
mode=versionanswers, andmode=queueis refused withAPI Key Requireduntil a key is presented. Happy to make any changes a maintainer with a device finds.Screenshots and the logo live at https://nzbfast.github.io/nzbfast/ and in the project repo; say the word and I will attach whatever sizes the App Store assets need. No gallery or icon files are committed here.