meeb

Most of the time, right now, yes. The uploader is from the video metadata and doesn't return a sensible name 100% of the time in practice. It's most of the...

That sounds a reasonable use case. I've not checked the feature stability support for a few months so I'll re-check to see if this is sensible to add now. Cheers...

Yes, but occasionally the uploader might be something like a random hash prefix or other seemingly nonsensical string. Likely, the string also needs to be `slugify()`'d before using it in...

Ah, thanks, yes that is a bug. Should be an easy fix I'll push a patch shortly.

The logic flow that causes this bug is a bit sticky, it's triggered when you've set a max media age to download on a source and then attempt to manually...

Bit messy, but you can always just actually delete the video file off the disk. It won't be automatically detected as missing and re-downloaded at the moment.

Yep a reasonable suggestion. The only reason this wasn't done already is I didn't want to have to handle log rotation manually in the container with yet another process, without...

Yes, via logrotate on the host machine. However the container can't assume logrotate is set up and configured on the host to manage the log rotations properly (e.g. via Docker...

Yes, logrotate can handle it if configured on the host quite easily. There's no way for logrotate no easily notify the container that the log has been rotated, but that's...

Cheers for the suggestion. You can handle this in Python with `TimedRotatingFileHandler` or similar and rotate based on file size or per day etc. with the standard `logging` library. However,...