Speaking as an American who has known an Irish, I can corroborate this with the fact that "film" is pronounced "fillum."
ASK_ME_ABOUT_LOOM
This project is so popular that it's preinstalled on every OS!
SSH key auth for terminal login, plus an nginx proxy and client cert auth on anything accessible by the outside world. I'll expose any internal service I want because nobody is getting through the client cert auth.
On my server, people don't have access to delete, so content tends to either fall into the category of "rewatchable" (classics, series, Oscar winners, etc) and "everything else." Even a given year's really popular Oscar winners will stop being watched after a period of time, and odds are good that nobody will watch it ever again. When is the last time someone with access to your server watched The Color of Water or The Life of Pi?
Storage may be cheap, but downloading is cheaper. There's nothing I've gotten that can't be re-gotten.
Libraries do the same thing with books, it's called "weeding." People get up in arms about the idea that a library would voluntarily discard a book until they learn that they're getting rid of titles like "An Expert's Guide to Windows NT." The librarian's response? If you like a book, check it out. Titles that are borrowed don't get weeded.
does it support white listing things?
Actually, yes! I got a really good suggestion on this and it now supports a whitelist of TMDB/TVDB IDs in a file called protected which you can volume mount when you call the container:
docker run --rm -it --env-file .env --network=host -v /home/user/protected:/app/protected ghcr.io/ask-me-about-loom/purgeomatic:latest python delete.movies.unwatched.py
:laughs in usenet:
Let's not pretend all of this stuff is high art. Look, if they really need to watch Krampus: Origins, they can download it again.
~~It does not. My suggestion is to either set your threshold high enough that the content gets watched, or put it in a separate library of special content you don't want deleted.~~
After a bunch of digging, I was able to find this documentation for configuring Slack integrations with shoutrrr, which is the notification system bolted on to scrutiny. After quite a bit more trial and error, I wasn't able to get token auth working (it appears shoutrrr's updated docs are already out of date), but I was able to make webhooks work. Gotta say, shoutrrr's configuration strings are awfully user-hostile.
After some more trial and error, I was able to get SMTP auth working after removing all special characters from my password and setting it to a stupidly long randomly generated string.
I used scrutiny years ago, but recall not being happy with it for some reason. I'll give it another try.
Edit: I remember now. The notification configuration is next-level awful. The documentation is close to nonexistent. Getting basic SMTP auth is non-functional. Finding an actual example of a slack notification configuration is impossible. Have any working configs you can share?
Gotta wonder how many people are down voting because they think the title is moralizing, when it's anything but that.