We have quite a budget collected over the last 5 years, and while we’re really happy to see so many in the Jellyfin community contribute to us, we want to ask you to stop!
No, really. We don’t actually need your money. At least, not here and now.
We have over $24,000 in the bank, and with average monthly expenses of only ~$600, that’s over 40 months (3.3 years) of runway! So, we have plenty of money for the near future.
Thus, at this time, we want you to seriously consider donating to the authors of Clients you use, instead of (or in addition to) the main project. Client support is the hardest part of the Jellyfin ecosystem to keep going, and most of them are maintained by only a single person or very small team. With the API changes in 10.9.0 and the upcoming 10.10.0 releases, they’re going to be very busy trying to keep up, and thus could really use your support in a way that the core project here doesn’t right now.
So, if there’s a client you use every day and that you love, consider finding it’s author in our list of official clients, and sending them a little something instead (or too).
No, this doesn’t violate our policy of “no paid development”, because donations are just that - donations. We will still not honour bug bounties or similar, and still not use our collective finance here for paid development. So don’t feel like you’re doing something wrong, you’re not!
I’ll leave this notice up until we drop to ~1 year (12 months) of remaining runway, at which time we can re-evaluate where we’re at.
Happy watching!
I personally would rather see then take some of the “extra” money and apportion it to suitable client projects themselves, but I can understand them not wanting to become financial administrators in that way.
I’m not sure, probably? I gave up on trying to setup the -arr suite in my cluster because I was having issues with sharing PVCs.
But I’d like to get everything playing nicely soonish. I was hoping for something all-in-one because each of the -arr apps has so much to configure, and there’s a ton of interchangeable parts in the space, and I’d rather not have the cognitive overload of all the decisions and have a config that just works™
Sharing PVC’s seems like an anti pattern. My suggestion would be to share storage by having network storage instead like a NAS and share that with the same user in all Deployments. Generally for each *arr you need a /data and a /config so the data should be same location in the shared network solution. Check out https://hotio.dev/ for ready solutions which you only need to supply with the storage basically. Default settings works for me.