So going back to the title, what to study? Maybe some specific book? Private classes/courses?

Networking. If you want to understand the reasoning behind things this is where you start. A good foundation in tcp/ip, the 7 layer network stack, as well as basic network protocols (dns, dhcp, http, etc.) will go a long way toward helping you troubleshoot when things go wrong.

Maybe throw in some operating systems study as well for when you start to use docker.

You’re talking a lot of storage - it might be worth investing in some low-end server hardware. A Dell tower or something, maybe one off eBay if you’re looking to cut costs.

I picked up a PowerEdge T110II a long time ago and it’s been… flawless. Just a simple server with a 4x4TB RAID5. No hardware problems (aside from occasional disk failures over the years), easy to manage. It costs a bit more - but server hardware is often just more reliable and for a NAS that’s job #1. This server just runs.

I just upgraded the memory in it to 32GB for ~$100USD. Before that it had 8GB. I needed more for restic doing backups. I probably could have gotten away with 16GB but I figured I’d max it out for that price.

Wow, this question takes me back to like the 00’s when laptops had battery life measured in minutes.

How about “no”.

This week - Apache Airflow setup to automate running backups (replacing cron).

I love how you came up with a completely different scenario to answer “yes” to .

Doubt

You willing to go to jail then? Or just asking others to do so?

When you open and read files from a program the OS (kernel) will typically cache part or all of those files in memory. This is to speed up subsequent reads of that file since disk access is slow.

“preload” seems to be making use of that feature.

The kernel maintains this cache and evicts (unloads) things from it as needed. You don’t need to worry about it.

Gonna make provisioning servers a lot more interesting…

Man, what’s up with Linux filesystem developers?

Compared to checks notes reinstalling an entirely different distro???

Jesus the cli phobia here is ridiculous.

While learning about all the Linux stuff I came to know about desktops, and I felt like, if I wanted to ever use a different one, yes, it could be installed the hard way, but I would rather have a distro that can be installed with my desired desktop by default, and the one that got my attention was KDE.

‘sudo apt install kde-full’ is “the hard way”?

I’ve been accused of “gate keeping” when I tell people that this is a shitty way to deploy applications and that nobody should do it.

Some people get into self hosting because they want their data to be their data. They don’t care about the particulars, they just want that peace of mind.

These people are the worst. What they want is fine - but the idea that you don’t need to worry about the particulars is ridiculous.

I think you could take this arbitrarily far.

This can be said about literally anything. And it’s a “slippery slope fallacy” to use as an argument.

There are “appropriate levels of understanding” I’m advocating for. I’m not even saying “don’t use yunohost” - just understand what the components you’re using do and how they interoperate.

How do you know that people do not read the scripts first and come to the conclusion “that is safe, nice that somebody build a convenience script I just need to read”?

🤣

Also, what can I expect concerning RAID? That is definitely the most concerning thing for me, as I’ve never worked with it.

Generally speaking it’s recommended these days to use a software RAID rather than relying on hardware. If anything happens to that RAID controller you will need to replace it with a duplicate in order to mount your drives. Software RAID is controlled by the Linux OS and would be much easier to recover. There used to be a bit of a performance penalty for a software RAID but these days it’s negligible.

That’s fair - I’ll keep that in mind in the future to be more clear.

Really grasping now aren’t ya?