Now you have me downloading 10GB of MP3.com pages so I can go searching for old albums. :D
Do you keep those releases separated from your main library (file-wise)? I'm trying to decide if it makes sense to segregate them and manage them completely outside of beets.
While I don't disagree with the need, what you're saying sounds an awful lot like "We need to drain the swamp and so what if he grabbed them by the pussy or some shit? You gotta do what you gotta do."
Watcharr is for building a backlog and recording what you've watched.
Seerr does let you build a backlog, but it's more for the users of your media server to be able to request items for acquisition. Once approved, it sends the request to be automatically downloaded and added to your library.
Now since you have me looking... I installed Watcharr and it's okay. Has a Discovery section. Easy to add things and mark them watched. But no stats, no integrations. It just seems a little barebones.
So I installed Yamtrack. The UI isn't really as intuitive to me and there doesn't seem to be a Discover function. BUT I love that it can track books, video games, and others as well. It also has Jellyfin integration.
I'm going to live with Yamtrack for a bit and see. It would be great to have a tracking app that also handles media requests. Seerr let's you build a watchlist, but it isn't all that helpful or fleshed out.
I have a Beelink Mini S that I got 4 or 5 years ago (N5095, 8GB RAM, 256GB SDD). It was $200 new at the time. It's easily handling the hosting of 20-25 services.
For the little that you plan on doing with it, I think you could grab just about anything.
Another vote for CWA. It's been a year and I can fully remember my reasons for not going with something else, but I tried several and nothing was quite as complete for what I needed.
I also don't want or need much for automation. I want to curate my library, there are few authors I'd want to monitor and grab everything from. Then from a metadata front, CWA lets me easily search for and cherry pick bits of metadata.
Navidrome server on the NAS. If I'm away from home and using a computer, I have it exposed to the internet and just use the web app.
On my home computer I've been using PsySonic lately and like it quite a bit. Quirks here and there, but it does get updates.
On my phone, and so just about everywhere, I use Symfonium. None of the FOSS apps I found last year did it for me. Symfonium is ridiculously customizable.
That still doesn't help me understand why you would clone the entire repo just to install the docker image. You create the compose file (and the variables file if that's how you roll) and docker handles the rest. For someone who is already admitting their unfamiliarity with things, the whole idea of getting comfortable with git just seems unnecessary and unhelpful in this context.
It's fine, you don't need to reply again. Just different outlooks, I guess.
No, I get that the repo isn't, but all you need to spin up the container is the compose file, right? I'm just trying to understand, not argue. I'm not completely comfortable with git, and just about "good enough" with Docker. So if I'm missing something, I'd like to learn.
Just curious, but why bother cloning the repo just to copy out the text of one file? For compose files I usually just copy & paste, then edit what I need.
If you aren't a big consumer of shows and movies, just use the free services if they fill the need for you. Personally, I've purchased hundreds of movies and TV shows on disc and digitally over the years. Jellyfin lets me put them all in one place for my whole family to access. No need to try to remember what service it's on or where the disc is.
Now you have me downloading 10GB of MP3.com pages so I can go searching for old albums. :D
Do you keep those releases separated from your main library (file-wise)? I'm trying to decide if it makes sense to segregate them and manage them completely outside of beets.