Releases: Xoconoch/spotizerr
2.5.1
2.5.0
2.4.0
So... 2.3 happened.
I pushed a completely broken version because my tests were running in non-fresh installs, so there was no way to detect the failure that caused 2.3 to be unusable.
Special thanks to @mustafasoylu for stepping in and saving the day, I have, and still will be pretty busy these days, so I definitely couldn't have fixed this sooner than him. In fact, I couldn't even push the patch until today.
In order for this to not happen again, I have now added a tests/ directory in the repo, it will not be present in any of the docker images, it is for development purposes only and to allow others to identify any flaw they might have.
Note that currently they are broken, but I just wanted to push this as soon as I could, they will actually work in the near future.
Changelog
Contributors
Assets 2
2.3.0
Changelog
- Now when a single track fails, the parent download is not stopped (like a playlist or an album)
- Reworked authentication flow, integrated spotizerr-auth
- Credentials are now stored in
creds/accounts.db. - Implemented region specification per account, preparing for region-based features.
- Spotify api keys are now global, not account-exclusive.
Migration
If migrating from >=2.2.1, you will have to re-setup your credentials. I recommend backing up the ./data/creds dir, since all necessary info for migration is contained there.
- Deezer arl: under
./creds/deezer/{accunt name}/credentials.json - Spotify search creds api:
./creds/spotify/{account name}/search.json - Spotify credentials blob:
./creds/spotify/{account name}/credentials.json
Re-enter those in the UI or, in the case of spotify, you can use the new util spotizerr-auth to make the process WAY less painful than before.
2.2.1
2.2.0
2.1.1
2.0.1
2.0.0
Hey guys, I've been cooking 2.0 during my absence and I think you are going to like it.
This version introduces major architectural changes including the implementation of Watchlist and History features, and a migration of frontend code to TypeScript (fucking finally).
New Features
- Watchlist:
- Monitor Spotify Playlists and Artists for new releases/tracks.
- Automatically queue downloads for new content based on configuration.
- New UI page (
/watchlist) to view and manage watched items. - API endpoints (
/api/playlist/watch,/api/artist/watch) to add, remove, list, and trigger checks for watched items. - Configurable watch settings (enable/disable, poll interval, artist album groups).
- Download History:
- Persistent storage of completed, errored, and cancelled downloads.
- New UI page (
/history) to view past download activity. - API endpoint (
/api/history) with pagination, sorting, and filtering.
- Duplicate Download Prevention:
- New tasks for items already in progress or in the queue are now detected.
- For manual requests, this creates an error task indicating the duplicate.
- For watchlist tasks, duplicate active downloads are automatically skipped.
- Credential Validation:
- Credential data (Spotify credentials.json / Deezer arl) is now validated when added or edited, including basic connection retry logic.
Improvements & Changes
- API Endpoint Structure: Download endpoints now use item IDs in the URL path (e.g.,
/api/album/<album_id>) instead of relying solely on a?url=query parameter. Metadata is fetched internally after receiving the ID. - Configuration Management:
- Configuration files and credentials are now stored under a new
./datadirectory (e.g.,./data/config,./data/creds). - New config options added for Watchlist.
- Configuration files and credentials are now stored under a new
- Frontend Technology Stack:
- I knew it had to happen someday, so what better time than now? Ported the frontend to Typescript.
- Introduction of new UI pages for Watchlist and History.
- Backend Rework:
- Refactored download functions (
routes.utils.album.py, etc.) to work with the new task management system. - Celery worker logging is now captured and directed to the main application logs.
- Added periodic cleanup task to manage Redis data size.
- Refactored download functions (
- Logging:
- Application logging setup improved to prevent duplicate handlers.
- Task-specific log files are now generated under
./logs/tasks/.
Installation & Deployment Notes
- New Directories: You must create the following directories before launching the containers:
data/creds,data/config,data/watch,data/history,downloads,logs/tasks,.cache. - Volume Mapping: Update your
docker-compose.ymlvolumes to reflect the new directory structure, particularly mapping./datato/app/data. - Dockerfile: The Docker build process now requires
nodejsandnpmto compile TypeScript. These are automatically installed by the updated Dockerfile. - Configuration File Location: Your
main.jsonconfiguration file should now be located at./data/config/main.json.
Here, get some screenshots my friend:
1.4.0
Bug Fixes
- Fixed a UI logic issue so error messages now display correctly.
- Corrected handling of “/” in playlist and path names to prevent unintended deletion of existing album tracks.
- Resolved a real‑time downloading bug that was deleting and re‑downloading preexisting album tracks.
- Fixed the %year% placeholder and replaced the outdated %album_artist% with %ar_album% in the configuration menu.
- Ensured numerical BPM values are no longer reported as invalid.
- Fixed creation of the .m3u file when downloading a playlist.
- Eliminated the “couldn’t write to .cache” warning by guaranteeing the cache file is created with correct permissions.
UX Improvements
- Cancel buttons now respond instantly and reliably.
- Progress reporting in the download queue has been enhanced for clearer, real‑time feedback.
- Features & Enhancements
- Added support for password‑protected Redis connections.
- Non‑English Spotify URLs are now recognized and handled correctly in search.
Update process
There is now a .env file necessary for the app to work, see the .env inner documentation in the repo or the one present in the README.