YouTube now gates downloadable formats behind JS challenges (nsig); yt-dlp
needs a JavaScript runtime (Deno — its only default-enabled one) to solve
them, and its STABLE channel can lag months behind a breaking YouTube change.
Users hit "Requested format is not available" on every stream and music-video
download with no hint why. Neither piece is fixable via requirements.txt:
Deno isn't a Python package, and a version floor can only ever resolve stable.
- Dockerfile: install Deno in the runtime image (official installer,
auto-detects amd64/arm64, build fails early via `deno --version` if it
breaks; unzip added for the installer) and build with the yt-dlp NIGHTLY
channel (`pip install -U --pre "yt-dlp[default]"`) on top of requirements
- core/youtube_client.py: one-time startup warning when deno isn't on PATH,
naming the exact failure it causes and the install command — instead of
letting users debug a cryptic yt-dlp format error
- requirements.txt: annotate the yt-dlp line with the stable-lag caveat, the
nightly upgrade command, and the Deno requirement
- README: Deno + nightly notes in Prerequisites and the Python (No Docker)
install section; Docker bundles both automatically
The AcoustID section in the README was a one-liner that did not
explain how to get the API key or why the retag action sometimes
appears to do nothing.
Expand the section with:
- A short paragraph pointing users at acoustid.org/new-application
and the Settings entry where the key belongs.
- A note cross-referencing issue #704: the retag path treats an
existing MUSICBRAINZ_TRACKID tag as a short-circuit, so removing
the cached tag is the documented workaround. This gives a
definitive answer until the retag path itself is fixed.
No code or behavioural change.
- Replace the shell convenience script with a cross-platform Python launcher.
- Keep dev.sh as a Unix compatibility wrapper.
- Let the direct backend bind with host and port overrides.
- Update the root and webui README guidance for the new launcher.
- Preserve the backend startup behavior used by the old dev flow.
- Introduce dev.sh as the local backend + Vite launcher
- Document the separate backend/frontend development flow
- Note that the dev Gunicorn config restarts Python on file changes
- Note that Vite hot reloads React changes in webui
Adds previously-undocumented features to the Key Features section:
- Hydrabase P2P metadata network (dev-mode alternative to iTunes)
- Genre Whitelist for filtering junk tags across enrichment sources
- Multi-artist tagging options (separator, multi-value ARTISTS, feat-in-title)
- Live Log Viewer in Settings → Logs
- ReplayGain analysis during post-processing
Expands the Automation Engine section with more trigger examples,
multi-THEN actions (up to 3 per automation), Signal Chains cycle-
detection behavior, and Automation Groups.
Expands Mirrored Playlists to cover Auto Wing It metadata fallback
and the per-track Unmatch button with DB persistence.
Adds a Release Channels section to the main README explaining the three
Docker image tracks users can choose from: stable :latest (Docker Hub),
nightly :dev (GHCR, rebuilt from dev branch), and pinned version tags.
Includes a decision table for picking the right channel and switching
instructions for docker-compose users.
Notes on the Unraid section that the template points at :latest by
default, and how to switch an Unraid container to the :dev channel
by editing the Repository field.
Adds a Contributing section covering the dev → main PR workflow, how to
branch off dev, expectations around ruff + pytest passing locally, and
how to run the dev gunicorn config.
Mirrors a short release-channels blurb at the top of
Support/README-Docker.md pointing at the main README's full guide.
All user-facing labels, docs, help text, tooltips, error messages, and debug
info output updated. Backend config keys, variable names, actual path values,
and Docker volume mounts are completely unchanged — zero functional impact.
Switch the web UI from Werkzeug's built-in server to Gunicorn for a more stable production deployment path.
Keep a separate dev config so local runs still reload quickly, while the production path uses a dedicated WSGI entrypoint and cleaner startup behavior.
The main motivation is to reduce the websocket teardown noise and make the server behavior more predictable under the app's mostly background-driven workload.
- AcoustID now runs for all sources, not just Soulseek/YouTube
- Metadata source is user-selectable, Spotify no longer auto-overrides
- Streaming match validation applies same scoring as Soulseek
- Playlist Pipeline automation added
- Live/Commentary Cleaner maintenance job added
- Discogs enrichment worker (10 workers total)
Updated _find_downloaded_file to resolve download paths for Docker environments, ensuring compatibility with host-mounted directories. Also updated README to clarify YouTube integration and sources.
Introduces a template-based file organization system for downloads, allowing users to define custom folder and filename structures for albums, singles, and playlists. Updates the backend, config example, web UI, and client-side validation to support template editing, resetting, and error checking. Improves consistency in file placement and metadata handling across all download modes.
Added a section explaining how to complete Spotify OAuth authentication when accessing SoulSync remotely via Docker. This provides a workaround for Spotify's redirect URI restrictions and guides users through the necessary steps.
Introduced DOCKER-OAUTH-FIX.md to address 'Insecure redirect URI' errors when using OAuth from devices other than the Docker host. Updated README.md to reference the new guide for users encountering authentication issues.
Added detailed setup guides for Spotify, Tidal, and Plex APIs, including step-by-step instructions for obtaining credentials and tokens. Clarified prerequisites and configuration steps to help users set up SoulSync more easily.
README now provides both docker-compose and direct Docker run options. docker-compose.yml switched from local build to using the published soulsync image for easier deployment.
