Note that Steam lets you ignore entire publishers. Go to the publisher page, click ignore. Done!

If you don’t want to test the round trip, have your fastapi routes call some other function and test just that function.

No disagree here. :)

As a counterpoint to no proxmox, I get a lot of utility in being able to entirely destroy and reprovision VMs. I get it adds a layer of complexity, but it’s not without its merits!

With respect to the media, you can mount the volume as read only, preventing Jellyfin from accidentally wiping your underlying content.

I just ran into this last night and discovered the solution as well. Unclear why they chose this migration behaviour!

Yes, modifying the value is going to break the mappings (see https://github.com/jellyfin/jellyfin/blob/master/Emby.Server.Implementations/Localization/Ratings/us.csv). Anywho, I think we’ve discovered the root of your problem. How you choose to rectify it I leave to you! Personally, I’d recommend suffixing your filenames with [tmdbid-123456] as per https://jellyfin.org/docs/general/server/media/movies/ and letting themoviedb.org handle it all for you.

https://github.com/jellyfin/jellyfin/blob/31aa44d23d12b5dbb5f9a131242cc82c9ef98f24/Emby.Server.Implementations/Data/SqliteItemRepository.cs#L2279 is what’s discovering similar content. If the InheritedParentalRatingValue is considered zero, it’s only going to match other content with the same value. Can you elaborate on “I did change the name of the key for the rating variable in the metadata to be ‘MPAA rating’ instead of the default which I think was ‘rating’ before since I found it confusing.”? I suspect we’re zeroing (ha ha) in on the problem.

Hey, I’ve worked in the recommendations/similarity calculations. Could you post a screenshot of the detail page for Inside Out? I suspect your media doesn’t have associated metadata (e.g. tmdb tags) that are used to power similarity calculations.