About
Versions (54)
v0.4.9
2024-07-15Project updates
- This ships the latest fixes for channel extractions by the amazing yt-dlp team.
- See below to manually trigger a refresh of your failed channels.
- Some users have reported problems for index mapping updates, particularly on bigger archives. To counteract issues like that, increase the memory limit defined in
ES_JAVA_OPTSfor ES so there is enough space to sync the index in bulk.- That is also represented in the official docker-compose.yml file, make the same changes as here.
- If you maintain any installation help, guides, templates or similar, please update it there too.
- Ideally make the change first before applying the update.
- This will trigger a rebuild for the
videoandchannelindexes at first start, as always this should be mostly automatic.- If you encounter any problems, see here.
- This will probably be the last release for some time. We’ll make a cut here to start refactoring things in the backend, and rewrite the frontend in a modern JS framework. Check the open issues and reach out if you want to help with that process
Added
- Added per channel page size, aka deactivating shorts or streams per channel, docs, by @Boo1098
- Added retry logic for failed download tasks.
Changed
- Changed behavior when changing the TZ (Time Zone) environment variable. Existing schedules will now get changed to use the new TZ value.
Fixed
- Fixed error when adding video not part of a channel, #741
- Fixed error when a previously failed download would raise an incorrect
FileNotFoundError, #752 - Fixed issue allowing retrying from cache on previously failed download.
- Fixed issue where version check task would never trigger depending on your TZ value and uptime.
Manual updates
As yt-dlp fixed all issues with channel extraction, you can run trigger a reindex for channels that have failed to index properly before, run python manage.py ta_fix_channels in your Tube Archivist container, e.g.:
docker exec -it tubearchivist python manage.py ta_fix_channelsThis will scan your channels and add faulty channels to the regular reindex queue. That should return in a few seconds, you will see ✓ task queued. Then you can monitor the reindex progress on your settings page and in your docker logs.