AllHailTheSheep

not really. you can disable the default jellyfin login and force it to use ONLY ldap.

you totally can use ldap or oidc it just requires more setup. you just ensure jellyfin and your source of truth talk on their own subnet, docker can manage it all for you. ldap can be setup to be ldaps with ssl and never even leave the docker subnet anyways.

and yes I suppose you could rely on whitelists, but you’d have to manually add to the whitelist for every user, and god forbid if someone is traveling.

ldap auth will work on tvs

or use the ldap auth plugin with your source of truth, put it behind a reverse proxy, protect it with fail2ban and anubis. there are ways of exposing it safely.

thanks for posting this!

interesting. most modern lcds have a shiny reflective layer behind the backlight for this reason, I wonder if they’re all modeled after toshibas design

yeah agreed. I’m fully in support of an open source discord alternative, it’s sorely needed, but expecting to vibe code real time communication tells me exactly which programmers have worked with real time systems before. RTC is not something you vibe code successfully haha.

there’s a .cursor directory in there with a rule specifically telling it to not mark generated code as generated. I can’t see how that could ever cause any issues /s

really cool idea. ty for sharing!

wow. that dude is a piece of work. made the mistake of clicking one of the links to his blog, and wow. there’s a stunning lack of knowledge or self respect there

is that a big pdu hes holding?

I think modern compilers do actually compile recursion to be equivalent with an iterative model.

edit: yes when possible they will compile to be iterative, but if it can’t be written iteratively it will be a series of calls and returns. depends on the specific type of recursion it looks like.

I haven’t looked at that GitHub but I’m familiar with most of the terms so here goes (verify them if you wish, I can’t promise full accuracy).

portable file server with accelerated resumable uploads: portable most likely means it’s easy to transfer from one server to another should you ever upgrade servers or anything else. resumable means you can pause the transfers if you desire.

dedup: it will automatically deduplicate files. so if you upload the same file twice it will just use the one you previously uploaded, saving space.

webdav is for distributed authoring and versioning. I don’t know a crazy amount about it but assume it means there’s some code in place that aids with collaboration as far as sending a file, working on it, and reuploading goes.

ftp: file transfer protocol.

tftp: trivial file transfer protocol. good for small things but iirc it’s not inherently secure

zerconf: plug and play. no messing with configs needed.

media indexer/all in one file: most likely indexes media uploaded and stores the generated thumbnails in one big file. most likely this is so it’ll be easier to transfer the install to another server if needed (you can move one big file containing all the thumbnails instead of a bunch of tiny ones).

no deps: no dependencies, everything you need is self contained in that repo.

again, double check things your curious about but that’s my interpretation of what most would agree is kind of just a keyword filled description lol

thanks, I’ll check it out!

interesting. what do you use as the model and how is that config set up? I’m not disinterested in trying it I just don’t know much about using it for workflows, is there an article you’d recommend?

I’m glad you found something that works for you but giving ai control over a git workflow sounds like a catastrophy waiting to happen, how do you ensure it doesn’t do something stupid?

there are lots of cheatsheets out there but the best way to learn commands is practice. different people will use different commands, so you may not need to spend time learning ffmpeg syntax whereas others find it invaluable. Google is your friend while learning. if you have a Linux question, chances are someone else has had the same question and posted about it online. as far as basics go, spend some time learning about grep and find, they are probably the two most valuable basic commands imo outside of the common ls/mkdir/etc.

as for sudo, it’s just “superuser do” so it’s essentially the same as hitting run as admin in windows. lots of times if you try to run a command without sudo that needs it, you’ll get a permission error which reminds you to run as superuser. it eventually becomes second nature to say “ah, this command needs direct access to a hardware device or system files” which means it’ll need to be run with sudo.

according to that page the issue stemmed from an underlying system responsible for health checks in load balancing servers.

how the hell do you fuck up a health check config that bad? that’s like messing up smartd.conf and taking your system offline somehow

almost done re setting everything up after a catastrophic failure (ended up replacing multiple drives, the CPU, the motherboard, the psu, and the ram).

now I’m just running long command after long command, waiting for drives to zero, ensuring extended smart checks pass on new drives, cloning to my backup drives…

this things been down for a few weeks and I’m so excited to have it back up soon!

anyways, moral of the story is, the 3-2-1 strategy is a good strategy for a lot of reasons. just do it, it may save your ass down the line.

you’re a lifesaver!! I swear I looked pretty hard on the internet for this exact solution without success. my apologies!!

thanks for the info!!!