have the data drive (movies, backups, etc) get decrypted with a keyfile from the system SSD. you’re safe to lose, throw away, sell your data drive and don’t have to bother with shredding the data. this takes hours for drives of any significant size.

used in on my PS4, was hoping I can make it a dedicated TV media player. had to give up, too slow, issues with playback, subtitles, UI, etc.

Imma be the problemXY guy here - ditch the https part. without it, you don’t gotta deal with certs, signing, shit that’s outside your LAN, etc. it’s your LAN, do you really need that level of security? who’s gonna sniff packets and shit on your LAN?

now all you need is pihole where you set up your hostnames (jellyfin.lan, nextcloud.lan, etc.) and nginx proxy that maps e.g. jellyfin.lan to 192.168.0.123:8096. both of them run plenty fine in docker.

no experiences with audiobooks, but for normal books what’s needed is the OPDS plugin. then book readers can access the books without manually downloading/importing 'em.

I am asking the dude doing the transcoding why he’s doing it. I am not waging a crusade against all dudes doing transcodings.

to answer your question, no, I don’t, all media I got is 1080p and all my devices can display it.

not knowledgeable about them things but normal movies and shows with multiple audio streams and subtitles play just fine with directplay, selecting them from the client works fine, etc.

the only reasons I know of for transcoding would be if you have ancient clients that can’t play e.g HEVC or something, or if you’re on shitty broadband and it ain’t feasible to stream 4K to a phone.

why are you transcoding at all? it’s the first thing I turn off on jellyfin (and previously plex) installs. negligible cpu usage on both server and client when directplaying content.

it also has the OPDS plugin, so compatible Android readers can get books directly off it

it’s using mpv under the hood, so I guess it should be able to play audio headless. I’m using allcast to cast to it and control it.

I’m using macast as a media renderer, for video and audio. don’t know if there’s a docker container for it.

this one, OP. no need to introduce the horror that’s a:

• hosted app (why?!)
• client app is electron crapware
• the client app doesn’t even have full functionality, you have to use the web UI for some tasks

edit: I’m obviously speaking about the bitwarden/vaultwarden horror. keepassXC is none of them things.

I used enpass for years and was a happy user. one day it prompted me for some re-authentication bullshit security theater. although in that instant it was an easy task, took me all of 10 seconds, it demonstrated a scary amount of power they had as I couldn’t bypass it and access my data. from that point on, its days were numbered.

the second issue is the export functionality that was seriously lacking and I had to resort to 3rd party converter tools to convert it to keepassXC; no way that flew by their QC, it had to be intentional.

kodi and its derivatives are not something you should be using. it’s shit software on so many levels and we should burn it in the deepest volcanos we got.

try one of these:

1. run lineageOS TV (konstakang images) on it and install regular ATV apps for the services mentioned. so, like googletv except there’s no spying and ads and shit.

2. create a normal linux box that has a DLNA sink e.g. using macast. there’s no remote control, you use your android/iOS device to send it stuff, like movie from Jellyfin or a youtube video, and it plays it back and allows some control (pause, play, rew/ff, etc)

3. dedicated Jellyfin box; same as 2) but boots right into jellyfin client. it can be run in TV mode where it reacts to only up/down/left/right/enter/back, via gamepad or remote controller. if yours isn’t recognised, you can emulate it with InputRemapper.

not familiar with how twitch does stuff.

you also have the option of installing a normal raspi distro and then using a wireless keyboard and mouse/touchpad to run it, but I am of the opinion that once the device gets placed by the TV, it loses all keyboard and mouse privileges and should only be operated via the TV’s remote.

using laptops as a forever-plugged-in device (regardless if workstation or server) isn’t the greatest idea. as an intermediary solution, like until you have something more permanent in place, sure. otherwise, look elsewhere.

limiting battery charge isn’t available on all laptop models and is aimed at preserving the battery’s functionality; it doesn’t solve the issue of a forever charged and never emptied battery. on the other hand, removing the battery on a lot of models limits their performance, significantly.

what is a viable solution is if you get a laptop board that runs at full power without battery, you can remove the board from the laptop, retrofit it with better cooling and additional storage (mini-PCI or M.2 to SATA adapters) and you end up with an energy-efficient server. but that requires a lot of work and is not something recommended for non-enthusiasts.

in short, sell it or swap it for something more adequate.

do you have a ballpark figure of potential savings in $/€ per annum? and for what hardware? I remember calculating something similar and I don’t think I broke $20 in total, so promptly forgot about it.

not a plex user but someone buried the lede here… to me, this is the neon sign that screams GTFO:

we noticed that you’ve accessed libraries in the past

what business of yours is it to notice my private comings and goings?! what other actionable intel do y’all keep in your logs?! bye!

I ran something similar a while ago; it automated the steps you’re describing so it downloaded every new video from the channels I’m subscribed to along with metadata. I gave that up as it’s hella inefficient. what I have now is just a media sink by way of macast and I can send videos for playback to my media PC. so if you don’t need those videos for archiving purposes, try it out.

don’t go with server variants of the OS. they are intended for boxes that work without display and keyboard, which you have. instead, install any normal distro you’re familiar with. it’s infinitely easier to fix something with the full GUI at your disposal.

this is just your first install, you will iterate, and through that process you’ll get better and leaner, in terms of underlying OS. think of it as training wheels on a bike, you’ll pull them off eventually.

wired connection only, leave wireless turned off, and assign it a static IP address.

don’t do containerS, do one container first. figure out where you’re gonna store the compose files, where it will store data, how you will back that data up, etc. then add another. does it fit into your setup? do you need to modify something? rinse. repeat.

casaOS, aside from it’s murky background (some chinese startup or sumsuch, forgot?) doesn’t provide that path forward nor allows you to learn something, too much hand holding.

good luck.