You are waaaay over-thinking this…

I’m happy you’re discovering the Linux CLI, but this is pretty ridiculous. mpv, vlc, mplayer, etc. all serve very different uses from jellyfin.

I don’t.

Clearly you don’t know.

If I wanted to run updates frequently I would run arch lmao. Even if I did apt update every day, debian stable doesn’t get that many updates.

You’re not updating for features you’re updating for bug and security fixes. That’s why Debian stable doesn’t have many updates. But the ones they do are typically important.

That’s… Not how it works… Debian is “stable” not “secure”. You use Debian so that is easier to run updates frequently since they’ll be unlikely to break things.

All systems, daily via a single ansible script. That’s apt update, upgrade and reboot if needed (some systems set to only reboot with a separate script so I can handle them separately).

Rarely have any sort of problems.

I’m going to go out on a limb and say that the world does not, in fact, need a BASIC transpiler…

No.

Sounds like you bookmarked the whole flippin’ Internet.

“The one that makes sense”

Patterns and principles are guidelines, not rules. You don’t want to just apply them blindly.

You need to balance principles. Over-applying the DRY principle can lead to more complex logic that’s harder to understand than if you just wrote code in-line.

God yeah - this hits hard with me. I work in a place where the DRY principle is chanted like a mantra and I have to push back against it constantly. It’s like the one principle jr. devs learn (along with “never hardcode anything”) that just gets applied to everything whether it makes sense or not.

"These lines of code are very similar, let’s factorize them ! "

“We should take three simple functions that run similar (but different) things and make them call a single large complicated function that takes a parameter that tells it how to execute!”

::shudder::

Then how do you know that “most streaming services don’t work on Linux?”

Something that can make troubleshooting DNS issues a real pain is that there can be a lot of caching at multiple levels. Each DNS server can do caching, the OS will do caching (nscd), the browsers do caching, etc. Flushing all those caches can be a real nightmare. I had issues recently with nscd causing issues kinda like what you’re seeing. You may or may not have it installed but purging it if it is may help.

It’s not resolving, play around with dig a bit to troubleshoot: https://phoenixnap.com/kb/linux-dig-command-examples

I’d start with “dig @your.providers.dns.server your. domain.name” to query the provider servers directly and to see if the provider actually responds for your entry.

If so then it may be that you haven’t properly configured the provider to be authoritative for your domain. Query @8.8.8.8 or one of the root servers. If they don’t resolve it then they don’t know where to send your query.

If they do, the problem is probably closer to home either your local network or Internet provider.

This is an awful analogy…

squeezing every last drop of resource form tired old hardware

This is such a myth. 99% of the time your hardware is doing there doing nothing. Even when running “bloated” services.

Nextcloud, for example, uses practically zero cpu and a few tens on mb when sitting around yet people avoid it for “bloat”.

I’m not sure how the *arr stuff works but hard links don’t let you “edit a file while preserving the original” - they let you have mulltiple paths to the same file.

$ echo "hello" > file1
$ ln file1 file2
$ echo "world" > file2
$ cat file1 file2
world
world

Does *arr have some sort of copy-on-write behavior? Some modern file-systems have de-duping behavior and copy-on-write built in that you may be able to save some space with.

But the point of topic 1 was to simplify. You can keep doing your hardlink stuff but standardize it and simplify setup/configuration. If you always do things in the same way it’s less complicated to keep track of and fix.

You’ve understood the difference in terraform/ansible, and yeah terraform is probably not going to be as helpful. Ansible would be much more likely to help. It can seem burdensome to have to write configuration files for things at first, but it forces you to do things in a way that is standardized and repeatable.

1. Simplify. You’ve made a system more complex than it needs to be. Copy files rather than working around hard link limitations. Use off-the-shelf backup solutions. Have a single file server with a known location for all your mounts. Etc.

2. Automate. Not with bespoke bash scripts but with tools like ansible and terraform. These tools are built to help manage infrastructure and configurations.

Everything is a file? Naah, everything is a hard link ! (Or inode? xD)

Hard links are files…

Well - it was nowhere near helpful.