Their reasoning is literally the second sentence on that page.
Note however that the
10.Y.Zrelease chain represents the “cleanup” of the codebase, so it should be accepted that10.Y.Zbreaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous10.Yreleases if required for later cleanup work
Any 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.
This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.
I had the opportunity to check out a bunch of S3 servers for work. For a quick summary, Garage was much faster than Minio in my tests but lacks advanced S3 features like object locking, versions or retention. Be sure to check what you need before switching.
Also, it’s CLI only as far as I know, so the same as Minio will be.
Use one artist for album artist. For the artist field, look up how to properly split entries. This is different for IDv3 vs Vorbis. Split the artists and Jellyfin will handle it fine.
It’s really a wild growth over the years. My current approach is twofold. Netbox to manage devices/VMs and associated info with service deployments using Ansible. You can use the info from Netbox as an Ansible inventory directly.
Previously I tried network diagrams (too low detail) and spreadsheets (terrible to modify) to document machines. And for serviced I’d have an install page on my wiki (apologies, the codeblocks are somewhat broken atm)
For 2d platformers, the virtio GPU with 3d acceleration might be OK.
Per the RSS specification the guid field is optional.
And if you do want to provide it, any string works. So just count up from 1, use the title, current date or whatever for that field.
Why is this here?
Edit: apparently that dude’s been doing multiple of those
3-2-1 rule also applies with external providers
Get on a few private trackers and make a request
Just FYI, unless you absolutely need anonymity from ICANN/the country owning the TLD I wouldn’t choose Njalla. Legally any domain you purchase is owned by them, that’s how they can keep your name from law enforcement requests. However, that also means in any dispute between you and Njalla they can just refuse to service you and keep your domain without recourse.
Normal domain registrars are regulated and if you purchase a domain through them you are its legal owner, if they don’t want your service they must still allow you to transfer the domain somewhere else. Any good registrar provides domain WHOIS protection and will only give out your name to legal requests by law enforcement, so I wouldn’t worry too much about that.
I started using Quadlets recently and it’s great to have declarative configs for containers all managed with systemd. It only gets good with Podman version 5 though, 4.4 doesn’t support .pod files, which I use quite heavily.
Not sure what Plex debrid does, but anything managed by a good service manager (like systemd) is more reliable than starting a shell session and hoping it doesn’t die.
Nested VMs stay performant about three levels deep, so do that as well.
I’d stick to using the host IP for communication between pods. It keeps the separation of different pods intact, makes it easier to add new services and if you ever get a second machine for containers you can continue doing it the same way just with a different IP.
I second TorrentLeech. It’s a great tracker
The AIO container is so terrible, like, that’s not how you’re supposed to use Docker.
It’s unclear whether OP was using that or saner community containers, might just be the AIO one.
Minecraft loves single core performance, so it will likely behave differently to most general benchmarks.
But that also makes dedicating a few cores to it and everything else to other services.
Nextcloud News with the accompanying app on my phone. I was lazy that day
Upgrade notes for 10.11 RCs
https://notes.jellyfin.org/v10.11.0_features