Yes.
avidamoeba
joined 1 year ago
This is becoming the Donald Trump of companies.
Perfect. That checks one more requirement on my migration checklist. 🥹
I don't know if you can do this with Jellyfin but this is what I could do with Plex:
- create an account for her
- create a new dir for her movies
- create a new movie library called "Mom's special" which watches this dir
- share the new library with her account
- share the rest of the libraries with her account
- drop the garbage in the special dir
In the end no one else sees Mom's special, while your mom sees everything and Mom's special.
I wouldn't do that because I'd be inevitably picking up breaking changes without my knowledge that I'd have to fix after the fact. Unless you're pulling from a tag I guess. Still storing along the playbook feels more robust. It's less likely to get any surprises. Also I'm working under the assumption that you want to write idempotent code so you don't get breakage when your rerun it, which allows to run it on a schedule, to ensure your config doesn't drift too much.
Wow, exciting news in the world of RAM! We don't get those every day anymore. 🥹
If I read this correctly, Immich is setup entirely through Ansible, no docker compose. That's fine, however if Immich changes something drastically in their setup topology, it'll be more work for you to implement those changes. For services that use docker compose, you could use Ansible to deploy a compose file in a dir, say /opt/immich-docker along with its requisite .env and other files. Then setup running it via systemd. Then when you need to update it, it's almost copy-paste from the upstream compose file into your Ansible repo.
Yeah but some of the samba mounting mechanism is outside of the kernel. The protocol deprecation might just be in a separate package. 🥹 I haven't checked.
Yes, and some of the sources are BDS themselves.
10 down, 100 to go.
Yeah and I do not recall knowing people who thought it would end well. It was universally viewed as a bad move as opposed to developing MeeGo or going Android.
It's way easier to figure that out than check ChatGPT hallucinations. There's usually someone saying why a response in SO is wrong, either in another response or a comment. You can filter most of the garbage right at that point, without having to put it in your codebase and discover that the hard way. You get none of that information with ChatGPT. The data spat out is not equivalent.