It’s a shame because the server worked great for my purposes (even has the DVR functionality I use in Plex!). I tried Jellyfin but the front end apps (Apple TV, Roku etc) are either non existent or very inferior compared to Plex. This can make it very expensive for people who don't have the funds to buy disks in groups of 6 at a time (my personal preference for a raidz2 zpool)
One more data point about BTRFS, is that it doesn't support parity-stripe based redundancy models (raid5/6, raidz, etc), which makes it less interesting for a lot of people.Īnother note about ZFS is that it doesn't allow for growing of parity-stripe based volumes (although there's a tweet referenced in TFA that notes there should be a pull request with that feature expected soon). > One data point about btrfs, FWIW: I've been using it since 2016, the only "issue" I had is that it forced a failing drive into read-only, while other filesystems didn't detect the upcoming failure, thank checksuming for this. It looks to me that their focus is increasingly on "collecting analytics" on their users behaviours (logging everything they watch) and providing ad-supported streaming services, instead of trying to provide the best self hosted media streaming service (as it was when I started using Plex). I'm a relatively long time Plex user (switched over from XBMC (now Kodi) to Plex in ~2011), but also immensely dissatisfied with the direction they've taken, focusing on growth to satisfy PE backers over the needs of the user base that enabled them to even qualify for any PE money.
Reddit plex media server build full#
They do get a lot of things right, but I tend to prefer a full OSS stack, so jellyfin instead of plex, and btrfs instead of ZFS.
Reddit plex media server build plus#
This would help for backups, and for overcoming low-bandwidth links.īut maybe it's the Internet that needs to be fixed, with public key routing and content-based addressing, plus "heavy" clients and light, dumb servers instead of pushing everything to the browser. I'd also like the option to have simple distributed storage, trough something like hypercore. More packaging efforts are needed before this can become reality.
The holy grail of a "perfect homeserver" for me would be to run everything in GUIX, with a declarative configuration I can locally test before deploying, and rolling back. Certainly saved me some time on maintenance, though I do see the limitations. No mention of LVM nor LUKS either, I guess the understanding is either still a bit superficial (everyone has their own areas of interest), or they didn't want to complexify the setup too much.įor self-hosting, I can recommend which makes easy some traditionally hard parts of self-hosting, though it is quite opinionated (which isn't always a bad thing). The main missing feature for me is caching on faster disks, though there are some ways to get that. One data point about btrfs, FWIW: I've been using it since 2016, the only "issue" I had is that it forced a failing drive into read-only, while other filesystems didn't detect the upcoming failure, thank checksuming for this. I didn't know some parts they mentioned, I guess I'll investigate :)
0 kommentar(er)
