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?

Probably because it’s not illegal.

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…

Their community still a cespool?

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.

No shit. Why would they even say that?

Ahhh, self doubt, my old friend…

“There is probably a better way” is a fairly common feeling. In fact there probably is a better way. But at some point you need to be pragmatic and be happy with “good enough”. Don’t let perfect be the enemy of good (enough) as they say…

That said - follow your intuitions as well that things could be done better. Don’t be afraid to just re-write a bunch of things to see if an idea works better. Like grouping things from some “common.php” into domain specific functionality (dates.php, db.php, etc.). Or re-working how your front-end works. Maybe read other code or ask for code review from people more experienced, or even from an AI (yes, yes, I know, but they can be useful).

One problem you can find yourself in is that you’ve created code that’s very difficult to understand, but since you’re “in it” right now you understand it completely. If you put the code down for a week or two and come back to it you may find it very difficult to re-learn. If using classes, creating a DAO layer, or some other pattern helps to make your code easier to read then it’s worth following.

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?