Finer scheduling control for sources
So I needed to reset my tasks because my tubesync went into a state where no tasks where worked on anymore. I think that there is an open issue for that already but couldn't find it just now.
My issue is to discuss if there would be a possibility for scheduling sources for fixed spots. I like to have them in a particular order on particular days to particular times. See this picture which hopefully explains this a bit more:
Before having to reset I went into my mariaDB and tweaked the tasks to the times in the picture.
Now instead of doing it again manually I invested the time to write an Update-Statement to do it for me.
If you want I can share that too, its working fine with mariaDB, but I don't know if it works with Postgres or SQLite.
But if Tubesync would allow the finer scheduling when configuring the sources in app, that would be amazing.
I realize this will not be top priority, neither should it, but its a wish I have nonetheless :)
There is substantial work underway to entirely replace the current workers system which should hopefully resolve the issue of tasks suddenly failing entirely. There currently aren't any direct plans to add a specific per source schedule. I'll pop it on the wishlist though. Thanks for the detailed explanation and issue.
After all this time there actually is a plan to implement this now, I've recently had time to work on migrating the tasks system after a year of being too busy which has this as a planned future feature. Sorry for leaving the issue hanging for ages.
Has any progress been made on this? My wife was on a Zoom call for work when I added a new (Large) source. Oops. It would be nice if I could do the following.
- Have a default time window for doing indexes and downloads 10:00PM to 6:00AM for example.
- Have the ability to do an immediate load that overrides the default time window on a source by source basis.
- Have the ability to suspend the running schedule to be restarted later
- Have the ability to open tasks and adjust their run time.
or maybe simpler, have tasks run from a cron scheduler type environment.
Not especially, it's still pending replacing the workers, sorry.