mic_check_one_two

You’ll need to do some config on the actual services as well. Mostly in regards to telling it how you want to add things to your wanted list, how it should search for files, how you want it to download files, how it should handle downloaded files to be compatible with your media server, etc… Docker-compose can do a lot, but the *arr services are too granular to define everything directly in the compose file. You’ll need to actually configure the services after they are booted up via docker.

My stack includes the following:
Prowlarr for tracker management. This defines the various search methods, and makes them available for the rest of the stack.
Seerr for media requests. This manages what shows/movies are on the stack’s search list.
Sonarr for TV shows. Seerr tells it what to search for. It takes the relevant trackers from Prowlarr, and uses them to search for wanted media. It grabs media from the search based on quality profiles. For instance, my profiles are set to exclude 3D media, because none of my screens can display 3D. This is synced with my torrent client for automated downloads. When a download is completed, it automatically creates a hardlink in the relevant media folder for my media server to find. It uses the specific naming scheme for the media program, so the program can automatically detect info about the files.
Radarr for movies. Same basic concept as Sonarr.
Cleanuparr for download management (and some basic malware protection). Tracks downloads’ ratios, and automatically removes them from my torrent list when the ratio/time threshold is met. It also tracks “slow” torrents and will automatically retry them if a torrent is stalled/slow for too long. Also does some basic “movie.mp4.exe” torrent checking, to automatically block malicious downloads that get grabbed by the rest of the stack.
Bazarr for subtitle downloads. Automatically analyzes my media, and finds matching subtitle files for my media server to use.

Each of these will require specific config steps. For instance, Prowlarr will need to know which torrent/usenet trackers you want to use. Sonarr will need to know how to interface with your download client, which files to grab based on quality profiles, and how to rename files during import.

I prefer to follow the advice from people who actually set up and maintain email servers: “Fucking don’t. It’s not worth it.”

Just get a custom domain and run it through an existing email provider.

40TB, but that’s way more than I would realistically need if I was better about deleting old content. I have shows saved that I haven’t watched in years. With the *arr stack, there is very little reason to keep a lot of media saved, because reacquiring it again in the future is dead simple.

Until someone does a repair using a non-conductive replacement part. If your ground is running through your sink, and your sink springs a leak, there’s a non-zero chance that the new install will be PEX instead of copper. Still up to code from a plumbing standpoint, but now people in the upstairs shower are getting shocked because the upstairs outlets are tied into ungrounded plumbing.

Yeah, if you’re 100% local, that’s basically the ideal use case for Jellyfin. Plex really shines when it comes to remote access. But if you never use that, then there’s very little reason to use it over Jellyfin.

Yup, just spin up a second Docker image for your porn Jellyfin server. Copy your transcoding settings over from the existing image, and point the new image at different media folders.

It literally gives you a gigantic “hey we want to sell your data. Do you want to allow that” prompt when you open it. They didn’t even make the “no, don’t sell my data” button grey and tiny like so many cookie prompts do. Plex went out of their way to put it up front and center, instead of quietly burying it in an obscure opt-out. There are plenty of perfectly valid complaints about Plex… But if a company wants to sell my data, (and here’s a spoiler warning: They all want to) this is how it should be handled.

And a Samsung TV app. There’s an entire branch of Samsung TVs that require side loading to get a Jellyfin app installed.

Didn’t even need to dig. As soon as I opened Plex in my browser, it gave me a giant full screen “hey we want to sell your data. Do you consent” page. I disagree with data sale in general, but at least they didn’t go out of their way to bury the opt out. In fact, they actually went out of their way to present the notification in a way that was impossible to miss. If you’re capable of reading, you’ll know what the popup is for.

Yeah, being a novice in the FOSS scene can be extremely frustrating sometimes. It can very easily start feeling like you’re reading documentation for a plumbus, where every single sentence seems to introduce a new term you’re unfamiliar with. And it often assumes you’re already intimately familiar with how these new terms work. So even just reading the documentation for one specific thing often means having fifty different tabs open, as you also have to read documentation about a ton of dependencies or terms.

Yeah, the sad reality is that Plex’s setup experience is much smoother. And when you’re trying to convert people, the single largest obstacle is often social inertia. So lowering the barriers to entry is extremely important. My mother-in-law would need to sideload the Jellyfin app onto her TV, but Plex is available right on its app store.

Luckily, you can run both side by side. Jellyfin for me and my more tech-literate friends, Plex for those who don’t know/don’t care to learn.