If you’re doing a fresh instance it will solve a lot of issues. Personally I run a Nextcloud instance which got its own 2TB SSD. I mounted the disk at /nextcloud, then used bind mounts in docker compose for db and NC.
If you’re doing a fresh instance it will solve a lot of issues. Personally I run a Nextcloud instance which got its own 2TB SSD. I mounted the disk at /nextcloud, then used bind mounts in docker compose for db and NC.
Which part is your problem, serving the media from disk, or transcoding and serving that stream?
It’d be in my book.
A big portion of that is caused by the drives, so you’d have to compare the empty QNAP vs your empty machine. Also, depending on which NAS appliance, check that the CPU is actually powerful enough to run all your services.
I doubt that.
will all my Jellyfin traffic go through the VPS and count as bandwidth used?
Yes.
Ah ok, sounds reasonable.
Do you actually need the GUI or is it simply a preference? Because investing 15 minutes in a proper ffmpeg script might be worth looking into.
Apart from that, what would that hybrid “ffmpeg-then-Handbrake” approach look like? What would be the goal here?
“Cloud” simply means it’s on other people’s machines.
No. Why do you think it is?
Back when I started this compatibility with clients was an issue; but I don’t use Android anymore. In any case, is this still an issue?
Um… How are we supposed to tell you if your unnamed DAV client will have problems with your unnamed new DAV server? Works fine for me.
That’s fine for you and me, but not for the masses.
Great. Now do 40 apps and try not to get them killed by the OOM mechanism. I’m not saying I like the fact that messages go through Google’s servers, but I’m afraid there is no equivalent FOSS solution.
At least on Android you have two options: you use Google’s notification API which lets your app sleep until the system wakes it back up on receiving a notification. Or you skip all that, then your app has to run in the background or you won’t get notifications. You can guess what this does to your battery.
Humans overall are extremely predictable. Other factors might aggravate this, but even without any tech involved it’s not looking good.
That seems to be the safer option.
The first is the act, the second is the state.
Apparently you meet very shallow people.
Announce it, whoever wants it comments under the post, after a set date collect all the usernames, randomly select one, contact via DM.
I haven’t tested that part of it yet, but the self-hostable StirlingPDF offers conversion from PDF to a number of formats.
The rest I use it for works fine, so maybe that could be an option.