This adds a very basic scheduler feature. It's based on what qbit_manage does, but simpler.
Adds 'mode' and 'scheduler_period' to the config file. Valid modes are 'run' which just runs the script once like normal and 'scheduled' which schedules the script to run based upon the 'scheduler_period' in minutes.
This is more proof-of-concept than fully ready. I think a few other things would need to be considered first:
All print statements go directly to console. It might make sense to also direct these to a rotating set of log files via logger for the last few scheduled runs or something.
Should mode be select able via the CLI? I think it might depend on if ebook/audiobook support is split between config files or uses a single merged one
This adds a very basic scheduler feature. It's based on what qbit_manage does, but simpler.
Adds 'mode' and 'scheduler_period' to the config file. Valid modes are 'run' which just runs the script once like normal and 'scheduled' which schedules the script to run based upon the 'scheduler_period' in minutes.
This is more proof-of-concept than fully ready. I think a few other things would need to be considered first: