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
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?
Dang, I didn’t realize there was a GitHub page. I guess I assumed that since it’s closed source, it wouldn’t be out there. That’s all you! I don’t have a GitHub account.
Definitely, the default view on sync for Reddit was “overview” and included both.
Yikes! I’m going to have to do more reading, I guess. My experience with snap is exclusively limited to installing certbot on RHEL.
Could you elaborate on snaps? I’ve used them here and there and people seem to have really strong opinions on snap that I just don’t understand.
Press and hold any menu item in settings and all of the markdown required gets put in your clipboard.
For anyone else who was curious how in the hell they linked directly to the settings page: you can long-press any specific menu item in settings and it will automatically add the code for linking directly to your clipboard!
per vendor “legitimate interest” toggle
Where is this toggle?
How are you currently searching & downloading content?
In my specific case, I’m subscribed to a usenet indexing service, which is hooked in to sonarr & radarr, which send downloads to sabnzbd+ to trigger the downloads. Overseerr just adds another layer, sending requests to sonarr/radarr.
That said, Overseerr will work with pretty much whatever your specific method is. Just hook it in and the services handle the rest.
You would just be another Overseerr user. At initial setup, you pull all of the users you’ve shared your Plex server into the Overseerr config. You can dig into the settings and tweak it - the number of movies a default user can request per day, number of seasons of TV, etc. I have mine set up to auto-approve all requests, but users can only request one season of TV and three movies per day, to avoid people abusing the service. In general I don’t have to touch it.
You’ve been recommended Ombi, but I recommend Overseerr instead. You can set it to permit them to only login using Plex auth (so no credentials for you to manage) and import your user list from Plex. It links up to radar or sonarr (and other stuff) for downloads. It can be configured to auto-approve downloads so you don’t have to do anything.
I’ve been using it for years now. It’s great.
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.