I'm wanting to set it up for around 20 households to share, and with transcoding that exceeds a single (cheap) node.
I'm wanting to set it up for around 20 households to share, and with transcoding that exceeds a single (cheap) node.
https://jellyfin.org/docs/general/post-install/transcoding/h...
The jellyfin DB itself is unfortunately sqlite instead of being DB agnostic. Maybe you could hack together something such that only one node handles writes and everyone else handles reads... if getting multiple cheap nodes gets your more bandwidth. I have to imagine that jellyfin fairly quickly stops being in charge of the media stream directly.
But yeah I think the transcoding and the size of your data pipe is the only "hard" part. The DB read/writes themselves are going to not be an issue (I think)
[1] https://jellyfin.org/posts/jellyfin-release-10.11.0/#the-lib...
Do not upgrade Jellyfin if you have a sizeable library. Backup first if you do.
The other aspect is you could share the media storage over NFS and have multiple jellyfin instances running for different houeshold groups.
With 2 or 3 nodes like that I think you could make it work.
For your use case, deploying multiple instances would be the way to go.